I had the same problem. The only way to solve it was to use the
Apache2::Reload module. By using this module, the apache that crashed is
killed and a new process is started immediately. However, this not solve
the real problem but the popup is not displayed.
Moreover, I'm using Apache 2.0.54 and mod_perl 2.0.1 (precompiled
version) on Windows XP and I had a lot of memory leak problem with the
Apache::ASP module. This module causes also an internal server error
when the cleanup_register handlers is called: it seems that Apache::ASP
has detected mod_perl 2 at startup and went back to mod_perl 1 at
sometime so he didn't call the right handler. Have you check your
error_log ?
Foo Ji-Haw wrote:
Hello all,
I have set up my MP2 application, which in the course of development
has been reasonably stable. But when I put it under reasonably load (I
have a daemon with 5 threads that call it periodically, and I browse
around the pages with 2 other collegues), sometimes I get this error
(see attached for the actually screenshot):
The instruction at "0x280877f1" referenced memory at "0x515ee28". The
memory coudl not be "read".
The application basically freezes at this point. Clicking on the OK
button seems to bring MP2 back to operations immediately. Looking at
the log, Apache seems to have restarted.
This is very annoying, as my app is generally ready to go, but
intermittent errors like this makes it otherwise. Nothing else is
capture in the log, so I don't know where to go to discover the culprit.
Can anyone please advise me on this? Appreciate it!
--
Stéphane GUIBOUD-RIBAUD STMicroelectronics
HPC/PMG/AP3 Grenoble
Tel.: +33 (4) 76 585 246 TINA: 041 5246
