I created a simple seven-line .htaccess file, and did 100,000 requests to a file in the corresponding directory with ab. All processes were perfectly stable in memory consumption. Then I do the same thing with a <Perl> section in the .htaccess file. 100,000 requests later my 12 processes had grown from 6.5M to 25.5M
My analysis of this is that mod_perl's perl sections are *always* run in the pconf pool, rather than running in the request pool as would be normal for .htaccess files. Consequently, all directive parsing and config merging will use the pconf pool, effectively resulting in a permanent expansion of that pool.
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
