DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19687>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19687 idle httpd childs consuming 100% cpu ------- Additional Comments From [EMAIL PROTECTED] 2003-10-14 18:44 ------- As an update, I ran gdb on several of the spinning httpd processes, and noticed it was stuck in an ImageMagick function, which was being loaded by mod_perl for a particular web application. After removing "use Image::Magick" from my mod_perl startup scripts, this problem was resolved. The interesting part was that the parts of the web application that made use of ImageMagick were no longer accessible. This seems to just be an issue with loading the module, not with actually using it. It was also interesting because only a small percentage of httpd processes would spin as described, and all processes would have to have loaded Image::Magick. Even though this was caused by Image::Magick, it seems to me like there's still possibly an underlying apache bug... I would have expected apache to have killed off a spinning child. I would have also expected these PIDs to be listed in /server-status. I'm not this bug's original requestor, so don't mark this bug resolved. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
