Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

Memory corruption #79

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

Memory corruption #79

GoogleCodeExporter opened this issue Apr 6, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

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
Copy link
Author 

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
Copy link
Author 

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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter