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

HandleResponse called on URL which is already erased #219

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

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Apr 6, 2015

There is a known bug where, under load, we end up calling HandleResponse on a 
URL that is already erased.  This currently causes a fatal check failure in the 
Apache process, with a message pointing to this bug.  Without the check 
failure, the apache process will livelock and eat all available CPU; we've 
chosen to crash and recover because it is less bad than livelock in practice.

We're interested in obtaining distinct stack traces produced by this failure in 
order to better understand the circumstances under which it occurs.  Please 
report the version of mod_pagespeed you were running when you encountered the 
problem.

Original issue reported on code.google.com by jmaes...@google.com on 25 Feb 2011 at 7:08

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Original comment by sligocki@google.com on 25 Feb 2011 at 7:36

  • Changed state: Started
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Original comment by sligocki@google.com on 3 Mar 2011 at 8:33

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Fixed in r505.

Original comment by jmaes...@google.com on 3 Mar 2011 at 11:16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment