Perrin Harkins wrote:
This problem was fairly intermittent a while back, but became a real problem after we revamped our ad serving code to store details of the served ads across subrequests via $r->notes(); Not realizing that $r->main() is kinda misleading in that it doesn't really point to the top level request, we created a wrapper around Apache::Subrequest::run() to include code to copy all the notes from the parent to the subrequest and vice-versa. This caused the segfaults to escalate.[EMAIL PROTECTED] wrote:This is a bug introduced by having to insert workarounds for segfaults caused by Apache::Cooke/mod_perl. I've been asking for help with this issue for off and on for months now.
I suggest you stop using Apache::Cookie and see if the segfaults go away. There are pure Perl modules that handle cookies well, and it's not an expensive operation. Apache::Cookie is probably overkill in most situations.
Btw when I mean escalate, i mean that the odds of any browser getting a segfaulting page were increased, not that they are random - a particular request - URI,User-Agent,Accept,Cookie, etc combo - consistently segfaults, at least for a few days.
While trying to debug this we replaced Apache::Cookie (i'm not certain if every instance of which, but I think we did) with regexes against $r->header_in("Cookie"), to no avail.
At this point we are using Apache::Cookie and not overriding Apache::Subrequest::run(), and this is working without the segfaults.
But, we just recently tried to add an additional call to Apache::Cookie for our ad system and they all came right back.
--
--
Daniel Bohling
NewsFactor Network
