On l�rdag, april 6, 2002, at 04:50 , Doug MacEachern wrote:
> >> >> To avoid this kind of random segfaults I would suggest that if there >> are >> any perl interpreters still running when we are shutingdown the first >> perl interpreter we don't actually cleanup after us (The system will). > > the system does not cleanup PerlInterpreters when apache restarts > itself, > this would case massive memory leaks. > > why do you suggest this?? are there known bugs with ithreads in > 5.8.0-tobe? A bug, not a bug hard to say. If you perl_destruct the main perl inerpreter while child interpreters are still running you get very weird effects because perl will rip away alot of the stuff that the children are using. (Especially on win32). So one would want all perl threads to stop before you actually start perl_destructing. I haven't thought of this as a bug really since it (I thought) only happens on shutdown. Nick added a patch that just displays a warning when you quit the main thread with running child threads. Obviously this cannot work for restarting apache. I guess one has to make sure that the main thread doesn't destroy any memory the childs are using when it exits? Arthur --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
