After installing module server becomes unusable

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install module and restart apache
2. Wait for a few minutes watching top
3.

What is the expected output? What do you see instead?
I expected server load to either remain the same or reduce.

What version of the product are you using (please check X-Mod-Pagespeed
header)?
0.9.0.0-128

On what operating system?
- Debian 5 64 bit, CentOS 5 32 and 64 bit

Which version of Apache?
- 2.2

Which MPM?
- prefork

Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.
- I installed this across seven servers, running CentOS 5 32 and 64 bit, and 
Debian 5 64 bit (all Xen guests).  In every single case, after a few minutes, 
the load shot up to ridiculous levels like 60 to 90 and there were hundreds of 
apache process.  In the end I had to uninstall from all servers.

Original issue reported on code.google.com by d...@zikula.org on 4 Nov 2010 at 5:05

[GoogleCodeExporter]

I got the same problem using prefork


 httpd -l
Compiled in modules:
  core.c
  prefork.c
  http_core.c
  mod_so.c

Original comment by charles....@gmail.com on 4 Nov 2010 at 2:35

[GoogleCodeExporter]

We had the same problem. Server techs attributed it to heavy I/O writing 
notices/warnings/errors to the apache error_log. 

Original comment by skyhawk...@gmail.com on 4 Nov 2010 at 8:31

[GoogleCodeExporter]

I get the same problem in Ubuntu 10.10 server 64 bit, and Centos 64 bit, both 
using prefork. Absolutely killed the servers.

Original comment by zac...@gmail.com on 5 Nov 2010 at 1:59

[GoogleCodeExporter]

Same problem here, except because of my low traffic it took about an hour to 
bring me down.

Original comment by GeekNigh...@gmail.com on 5 Nov 2010 at 4:02

[GoogleCodeExporter]

This wasn't a traffic issue for me, although low traffic may delay it 
happening. Running on my test server several pages were delivered OK but then 
one page request triggered the problem (actually a missing page, error 404). 
All 4 processor cores went up to 100% load. Closing the page made no difference 
- load stayed high. Repeatable - happened whenever that particular page was 
requested. Ubuntu 10.10 Desktop 64 bit. Apache 2.2.16

Original comment by bobhawke...@gmail.com on 5 Nov 2010 at 10:22

[GoogleCodeExporter]

http://code.google.com/p/modpagespeed/source/detail?r=146

Note: this fix has not been made available in binary form yet.  We will release 
new binary distributions incorporating these changes on Monday Nov 8.

Those building using the open-source instructions on 
http://code.google.com/p/modpagespeed/wiki/HowToBuild can try out these 
improvements immediately.

Original comment by jmara...@google.com on 5 Nov 2010 at 10:50

• Changed state: Fixed