Skip to content
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

compcache: Decompression fails during suspend/resume #13

Closed
GoogleCodeExporter opened this issue Aug 21, 2015 · 4 comments
Closed

compcache: Decompression fails during suspend/resume #13

GoogleCodeExporter opened this issue Aug 21, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Engage compcache with some memory intensive tasks
2. Suspend to RAM
3. Resume from RAM. Some of the times, compcache decompression fails and
one of the big memory hog process (usually firefox-bin) will die.

What is the expected output? What do you see instead?
Resume should proceed without errors and there should be no swap-in errors.

What version of the product are you using? On what operating system?
compcache-0.4, 2.6.26.3, x86_64

Please provide any additional information below.


[117068.638324] compcache: Decompression failed! err=-6, page=93709, len=1354
[117068.638333] Read-error on swap-device (252:0:749672)

Original issue reported on code.google.com by dev...@gmail.com on 30 Aug 2008 at 4:56

@GoogleCodeExporter
Copy link
Author

Can you please check if this issue is still present in compcache-0.5.1?

Original comment by nitingupta910@gmail.com on 2 Feb 2009 at 1:53

@GoogleCodeExporter
Copy link
Author

This happened may be couple of times. So, its not really a reproducible bug. I 
have
just moved to 0.5.1. I would like to keep this bug open for few weeks to see if 
I
ever hit it again.

Do we have enough stats in place that we can catch it when it happens next?

Original comment by dev...@gmail.com on 2 Feb 2009 at 5:17

@GoogleCodeExporter
Copy link
Author

> Do we have enough stats in place that we can catch it when it happens next?

Not really - no extra code instrumentation to catch it better. But if this 
happens
again, we can surely add some debugging :)



Original comment by nitingupta910@gmail.com on 16 Feb 2009 at 8:26

@GoogleCodeExporter
Copy link
Author

devsku: please reopen if you hit this again.

... and here goes another victim of my bug closing spree :)

Original comment by nitingupta910@gmail.com on 26 Feb 2009 at 6:07

  • Changed state: Done

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

No branches or pull requests

1 participant