stas 2004/09/27 14:40:27
Modified: todo features_maybe
Log:
todo
Revision Changes Path
1.10 +10 -0 modperl-2.0/todo/features_maybe
Index: features_maybe
===================================================================
RCS file: /home/cvs/modperl-2.0/todo/features_maybe,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -u -r1.9 -r1.10
--- features_maybe 22 Sep 2004 01:37:02 -0000 1.9
+++ features_maybe 27 Sep 2004 21:40:27 -0000 1.10
@@ -2,6 +2,16 @@
# Nice to have features #
#########################
+* If Apache::SubRequest::DESTROY gets invoked more than once on the
+ same object (directly and indirectly via object's exit of scope),
+ memory gets corrupted and some later unrelated requests get affected
+ badly (segfaults in unrelated areas). So we probably need to do the
+ same handling as APR::Pool, where we make sure that no matter how
+ DESTROY is called, it's always called only once, any consequent
+ calls can be made a NOP or assert. BTW, it's easy to reproduce the
+ problem, by simply calling $subrequest->DESTROY 3 times or so in a
+ raw, the server just hangs...
+
* APR::BucketAlloc object returned by $r->connection->bucket_alloc
doesn't have a real package. It's OK for now, but when used outside
httpd, where that allocation should come from?
