perl-modperl-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From go...@apache.org
Subject svn commit: r125534 - /perl/modperl/trunk/todo/bugs_mp /perl/modperl/trunk/todo/release
Date Tue, 18 Jan 2005 19:03:09 GMT
Author: gozer
Date: Tue Jan 18 11:03:07 2005
New Revision: 125534

URL: http://svn.apache.org/viewcvs?view=rev&rev=125534
Log:
The reported PerlRun leakage isn't a release blocker, so move it to
bugs.


Modified:
   perl/modperl/trunk/todo/bugs_mp
   perl/modperl/trunk/todo/release

Modified: perl/modperl/trunk/todo/bugs_mp
Url: http://svn.apache.org/viewcvs/perl/modperl/trunk/todo/bugs_mp?view=diff&rev=125534&p1=perl/modperl/trunk/todo/bugs_mp&r1=125533&p2=perl/modperl/trunk/todo/bugs_mp&r2=125534
==============================================================================
--- perl/modperl/trunk/todo/bugs_mp	(original)
+++ perl/modperl/trunk/todo/bugs_mp	Tue Jan 18 11:03:07 2005
@@ -8,7 +8,12 @@
 * PassEnv/SetEnv propogation in <Perl> section 
   http://www.gossamer-threads.com/archive/mod_perl_C1/dev_F4/%5BMP2_BUG%5D_PerlPassEnv_issues_P70500/
 
-
+* there was a report about PerlRun leaking memory. the reporter didn't
+  give any more details, but I suspect that it's due to
+  ModPerl::Util::unload_package() which perfectly fits the timing when
+  the leak was introduced (when PerlRun started to use unload_package).
+  
+  Report: http://gossamer-threads.com/lists/modperl/modperl/77162
 
 * most of the xs wrappers print no "Usage: " when wrong args/wrong
   number of args are passed, would be nice to add the usage message

Modified: perl/modperl/trunk/todo/release
Url: http://svn.apache.org/viewcvs/perl/modperl/trunk/todo/release?view=diff&rev=125534&p1=perl/modperl/trunk/todo/release&r1=125533&p2=perl/modperl/trunk/todo/release&r2=125534
==============================================================================
--- perl/modperl/trunk/todo/release	(original)
+++ perl/modperl/trunk/todo/release	Tue Jan 18 11:03:07 2005
@@ -4,8 +4,3 @@
 
 -- see also todo/api_status
 -- see also todo/release-checklist
-
-* there was a report about PerlRun leaking memory. the reporter didn't
-  give any more details, but I suspect that it's due to
-  ModPerl::Util::unload_package() which perfectly fits the timing when
-  the leak was introduced (when PerlRun started to use unload_package).

Mime
View raw message