in reply to CGI::Application + mod_perl =|!= memory leak
Server version: Apache/1.3.27 (Win32) Server built: Oct 3 2002 18:55:42 Server's Module Magic Number: 19990320:13 Server compiled with.... -D HAVE_MMAP -D USE_MMAP_SCOREBOARD -D NO_WRITEV -D NO_OTHER_CHILD -D NO_RELIABLE_PIPED_LOGS -D HARD_SERVER_LIMIT=1024 -D MULTITHREADwith MOD_PERL = mod_perl/1.27_01-dev
and I tried your code as you had it set up, and I was getting leaks.
I also tried it under Apache::Registry, and I was getting leaks.
I also tried it as straight cgi, and still, I was getting leaks.
Then I thought, hmm, so I tried even the simplest of cgi programs under cgi/mod_perl and I was getting leaks.
I'll try Apache2 later, maybe my luck will change and i'll be more helpfull.
I suggest you try running it under Apache::Registry and as straight CGI, and then inquire on the module's mailing list cgiapp-subscribe@lists.erlbaum.net and maybe the mod_perl mailing list.
Good luck.
update: btw, perl -MCGI::Application -e"die $CGI::Application::VERSION" yields [Thu May 22 00:20:15 2003] -e: 3.0 at -e line 1.
|
MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy. |
|
|---|