Thanks, I have continued testing, and I can confidently say that the problem is definitely not an out-of-memory issue. The new dev version you sent is segfaulting about once for every 100 page requests in dev now, with no load except me clicking around, on a machine with 2G total RAM and plenty of free memory. The segfaults have occurred during pretty much every type of page request, and also not occurred on those same requests. Hitting refresh will always result in the page being correctly sent, with not segfault, on at most a couple pushes. Did you get the back-traces I sent? I sent them to your personal account, but I realized that you may check the list more. Every back-trace points to "EMBPERL2_Node_appendChild .... at epdom.c:2835" as the point of segfaulting. The only Embperl tags I ever use are the PerlBlock '[* *], [+ +], [- -]' tags. Is there someway I can bypass this 'epdom' code all together? (I don't see any reason for dom-parsing) This is pretty scary. Thanks, -Carl
----- Original Message ---- From: Gerald Richter <[EMAIL PROTECTED]> To: BeeThere Admin <[EMAIL PROTECTED]>; embperl@perl.apache.org Sent: Wednesday, March 15, 2006 11:28:50 PM Subject: RE: Intermittent Segfaults > > I noticed segfaults in my error logs a couple days ago. I am > getting 1 for about every 1K page views. I am able to > reproduce it now, but still can't make any sense of it. I'm > sending a backtrace, and my environment. > I will send you my current development version per private mail, because it contains some more checks for out of memory conditions. Please install it with perl Makefile.pl debug make make install This will give additional informations in the backtrace, in case the the segfault happens again. If you still get the segfault, please send me the backtrace again Gerald ** Virus checked by BB-5000 Mailfilter ** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
