DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31247>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31247 Intermittent Segmentation Faults in mod_cgi ------- Additional Comments From [EMAIL PROTECTED] 2004-09-22 14:11 ------- Some updates/corrections: 1) Yes, it's been compiled from source, without any patches. 2) There are two separate cgi scripts on our index page, one does banner rotation for a banner, it is included four times (once each for 4 banners), the other creates a list of links based on the amount bid for placement, it's included twice. The first script uses a text file db, while the second script uses MySQL. Both are included with virtual includes. Here's a sample of one of the sections with the includes (I can't give you the scripts themselves, they were purchased from someone else). <!--#include virtual="/cgi-bin/ads/run.cgi?id=homeworkersa2"--> <!-- homeworkersa2 --> </CENTER> <!--#include virtual="/cgi-bin/search/include.cgi?keywords=main&desc=1&url=1&cost=1&show=1&include=1" --> <CENTER> <!--#include virtual="/cgi-bin/ads/run.cgi?id=homeworkersa3"--> <IMG SRC="/images/spacer.gif" WIDTH="160" HEIGHT="5"> <!--#include virtual="/cgi-bin/ads/run.cgi?id=homeworkersa4"--> <!-- homeworkersa4 --> </CENTER> <hr class="green"> <!--#include virtual="/cgi-bin/search/include.cgi?keywords=main&start=1&bt=10&desc=1&url=1&cost=1&show=9&include=1" --> 3) I tried the advice in bug 29962, it didn't help at all. I'm still getting processes that bloat up to a huge size and I don't think it's related to sending large files through the server. We only have a two scripts that I know of that send out large files and neither one appears to be accessed as often as these processes appear (I often have to restart apache multiple times during the day, it take as little as 5 minutes or as long as several hours to nearly exhaust all available memory). 4) We've upgraded to 2.0.51 as of this morning, I'm still seeing the memory problem and the segmentation faults. I'm going to attempt to create another core dump with the new httpd. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
