Bug 846045
| Summary: | [abrt]: BUG: Bad page state in process firefox pfn:10563e | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Oliver Henshaw <oliver.henshaw> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:04d5b5db83f5b1f870a851c8feff868e9c46debe | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-11-14 20:28:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Oliver Henshaw
2012-08-06 16:12:06 UTC
I wrote a comment in abrt but it got lost: is this a bug? I see a comment I made for a recent oops report (bug 845343) did not make it to bugzilla either. Here is the comment, pasted from ~/.abrt/spool: Firefox memory use went crazy, mainly due to some yahoo mail/toolbar javascript suddenly eating up nearly 2GB (on a machine with two users logged in, leading to: $ free -m total used free shared buffers cached Mem: 7479 6477 1002 0 19 284 -/+ buffers/cache: 6174 1305 Swap: 6143 2 6141 The kernel is tainted by an earlier warning due to bug 715137. These sorts of bugs are a really obscure, and a lot of the time when we see them they are indicative of some kind of hardware fault (like memory going bad). That said, they can also occur from memory corruption caused by actual bugs. Can you update to 3.5 and see if you can reproduce it ? (If you have time, an overnight run of memtest86 might be a good thing too, just to rule out bad memory) disregard the comment about 3.5 for now, we haven't pushed an update for 16 yet. There's a few bugs we want to get worked out in f17 before we backport. Did memtest turn up anything? Otherwise you can grab the current F17 kernel and see if it fixes the issue for you. Memtest didn't turn up anything. Haven't had the oops again, but then I haven't had the runaway firefox memory again. # Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient). With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report. |