New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory corruption #79

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Apr 6, 2015

We don't have repro steps, but there are indications of possible heap 
corruption in mod_pagespeed.so.  This issue is to track investigation and 
progress.

Original issue reported on code.google.com by abl...@google.com on 13 Nov 2010 at 12:42

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Thanks for opening this issue although the behaviour is that many apache 
threads are opened and the server gets massively overloaded, could that be 
related to a memory corruption?

How do we test this? I would like to use mod_pagespeed asap.

Thanks for all the efforts.

Original comment by nickz...@gmail.com on 16 Nov 2010 at 3:17

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

In 0.9.8.1-r215 we added more memory debugging infrastructure, and found and 
fixed a heap-corruption bug.  Please re-open or add a new bug if another case 
is found.

Original comment by jmara...@google.com on 17 Nov 2010 at 4:45

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment