I have written a large web service application entirely written in Perl, build as Apache::Registry under mod_perl-1.99_11 build with perl 5.8.0 under Apache 2.0.47, all compile with Microsoft visual C++ 6.0.
The same application run fine without too much memory leak on Linux (Apacge 1.3.x, mod_perl 1.27, perl 5.8.0) and Apple Mac OS/X, even on Solaris 8.0.
On Windows, that's another story. Each connection to Apache, the Apache process clone himself and double the amount of memory required to run. Worst, the memory is never released back to the OS until the Apache service is restart or until the computer is put on his knees. What's going wrong? I did not want to use Apache 1.x on Windows because of the threading issue.
It look like a threading issue related to perl. I have a very small perl program which create thread and each thread created double the amount of memory required by the program. Does anybody have any clues?
Thanks -- Dany Ayotte, Teamsoft Inc.
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
