I added this line just before line 17570 that was causing the exception: mlog (0,"%%%%%%%%%%%DEBUG: itime= $itime maxBombSearchTime = $maxBombSearchTime text = $text regex = $regex");
I then let it run for a bit, until it crashed again with an out of memory error. The result, extracted from my log file (spat out by the line above), can be seen here: http://ilovewbpf.com/memory.txt The $text contains what is clearly a spam email. The $regex, is, I think what is causing the problem. It is 7,681 characters long - the contents of my bombRe- and when this is being combined with a relatively large email, it's just more than the Perl regex engine can handle. I'm going to reduce the contents of my bombRe and see if this solves the problem. At 12:22 AM 3/19/2010, Scott MacLean wrote: >I've now got 7 examples logged of this problem occurring, and every >time, it's line 17570 that is causing the out of memory error. This line is: > > while (time - $itime <= $maxBombSearchTime && $text =~ s/($regex)//) { > > >At 10:09 PM 3/18/2010, Scott MacLean wrote: > > >Doing some research into this "Out of memory!" error from Perl, it > >apparently only happens when a malloc() call within Perl fails, > >because memory it wants is not available. > > > >That said, my ASSP normally trundles along with about 2 GB of > >physical memory available, and about the same amount of virtual > >memory available. My MRTG logs don't show a sudden ramp up at the > >time of the crashes, in fact, they don't ever show anything other > >than a straight line in terms of memory usage. Unless a function > >within ASSP is suddenly causing Perl to say, "hey, I need 4 GB of > >memory, right now!" I can't see why Perl would be failing with this error. > > > >I'm at a loss. > > > >At 06:20 PM 3/18/2010, Scott MacLean wrote: > > > > >AHA. This one did the trick. I logged several hours of resets, and > > >the same thing shows each time: > > > > > >Mar-18-10 16:01:15 [Main_Thread] Info: Main_Thread got connection request > > >Out of memory! > > >Callback called exit at assp.pl line 17570. > > > > > >Now this is interesting...because the server has lots ( > 2GB > > >physical) free memory available while ASSP is running, and did at the > > >time of the error, as well. > > > > > >Is there a separate constraint within ASSP that is limiting its > > >memory use, in a way that will cause Perl itself to fault this way? > > > > > > > > >At 01:21 PM 3/18/2010, Scott MacLean wrote: > > > > > > >I'm going to try this again, but I'm going to get rid of the start > > > >/wait, so that the perl process outputs its entire console output (as > > > >well as redirecting the STDERR output) into the debug file instead of > > > >opening in a second window, and see if there is something to > see that way. > > > > > > > >At 07:50 AM 3/18/2010, Scott MacLean wrote: > > > > > > > > >I tried this (although I changed "delete" to "del" to make sure it > > > > >functioned correctly). > > > > > > > > > >It died three times overnight and duly restarted itself - but did not > > > > >log anything to asspdbg.log. It is a zero-byte file. assprst.log held > > > > >exactly what you expect: > > > > > > > > > >Thu 03/18/2010 0:54:04.13 > > > > >Thu 03/18/2010 3:00:51.20 > > > > >Thu 03/18/2010 7:37:27.56 > > > > > > > > > > > > > > > > > > > >At 10:12 AM 3/17/2010, GrayHat wrote: > > > > > > > > > > >@echo off > > > > > >pushd c:\assp > > > > > >:LOOP > > > > > >start /wait perl assp.pl >>asspdbg.log 2>&1 > > > > > >echo %DATE% %TIME% >>assprst.log > > > > > >delete pid > > > > > >goto LOOP > > > > > > > > > > > >that should pretty much solve the issue, just > > > > > >run ASSP through the above script, then check > > > > > >the resulting asspdbg.log file to find out any > > > > > >error message(s) (probably coming from a > > > > > >perl module) that would help pinpointing the > > > > > >cause of the issue; the "assprst.log" file will > > > > > >also contains all dates/times of restarts so > > > > > >it may ease searching through the log file > > > > > > > > > > > > > > > > > > > > > > > >------------------------------------------------------------------- > > > > > ----------- > > > > > >Download Intel® Parallel Studio Eval > > > > > >Try the new software tools for yourself. Speed compiling, find bugs > > > > > >proactively, and fine-tune applications for parallel performance. > > > > > >See why Intel Parallel Studio got high marks during beta. > > > > > >http://p.sf.net/sfu/intel-sw-dev > > > > > >_______________________________________________ > > > > > >Assp-test mailing list > > > > > >Assp-test@lists.sourceforge.net > > > > > >https://lists.sourceforge.net/lists/listinfo/assp-test > > > > >------------------------------------------------------------------- > > > > ----------- > > > > >Download Intel® Parallel Studio Eval > > > > >Try the new software tools for yourself. Speed compiling, find bugs > > > > >proactively, and fine-tune applications for parallel performance. > > > > >See why Intel Parallel Studio got high marks during beta. > > > > >http://p.sf.net/sfu/intel-sw-dev > > > > >_______________________________________________ > > > > >Assp-test mailing list > > > > >Assp-test@lists.sourceforge.net > > > > >https://lists.sourceforge.net/lists/listinfo/assp-test > > > >------------------------------------------------------------------- > > > ----------- > > > >Download Intel® Parallel Studio Eval > > > >Try the new software tools for yourself. Speed compiling, find bugs > > > >proactively, and fine-tune applications for parallel performance. > > > >See why Intel Parallel Studio got high marks during beta. > > > >http://p.sf.net/sfu/intel-sw-dev > > > >_______________________________________________ > > > >Assp-test mailing list > > > >Assp-test@lists.sourceforge.net > > > >https://lists.sourceforge.net/lists/listinfo/assp-test > > >------------------------------------------------------------------- > > ----------- > > >Download Intel® Parallel Studio Eval > > >Try the new software tools for yourself. Speed compiling, find bugs > > >proactively, and fine-tune applications for parallel performance. > > >See why Intel Parallel Studio got high marks during beta. > > >http://p.sf.net/sfu/intel-sw-dev > > >_______________________________________________ > > >Assp-test mailing list > > >Assp-test@lists.sourceforge.net > > >https://lists.sourceforge.net/lists/listinfo/assp-test > >------------------------------------------------------------------- > ----------- > >Download Intel® Parallel Studio Eval > >Try the new software tools for yourself. Speed compiling, find bugs > >proactively, and fine-tune applications for parallel performance. > >See why Intel Parallel Studio got high marks during beta. > >http://p.sf.net/sfu/intel-sw-dev > >_______________________________________________ > >Assp-test mailing list > >Assp-test@lists.sourceforge.net > >https://lists.sourceforge.net/lists/listinfo/assp-test >------------------------------------------------------------------------------ >Download Intel® Parallel Studio Eval >Try the new software tools for yourself. Speed compiling, find bugs >proactively, and fine-tune applications for parallel performance. >See why Intel Parallel Studio got high marks during beta. >http://p.sf.net/sfu/intel-sw-dev >_______________________________________________ >Assp-test mailing list >Assp-test@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
