Bug 79491
Summary: | Sessions shut down for "Out of Memory" error | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <scollins> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | michael, scollins |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-03-01 22:23:25 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
Need Real Name
2002-12-12 12:07:13 UTC
Ick - it is the behaviour of the kernel to salvage a running system by nixing off processes to free memory. This is to prevent complete system instability. Could you please provide the output of your /proc/meminfo after having the system up and running for a while? Run xdpyinfo, check whether you have a RENDER extension. If not, gnome-terminal and other GNOME apps leak memory. The workaround is IIRC to use konsole or xterm instead of gnome-terminal. Note that other apps reportedly suffer from the leaks too, but gnome-terminal is usually the most severe. 'kernel: Trying to vfree() nonexistent vm area (e02bd000)' is the start of the kernel running into problems. That shouldn't normally happen. Are you 100% sure that the memory in the system is reliable? If so, and you see the same behaviour with different memory modules in place as well, please re-open and submit the entire 'oops' message. Thanks. Memory modules have been swapped and replaced. The intermitent problem remains. We've switched to KDE from GNOME on the advice of Miloslav and are waiting to see if this reolves the problem. We have not been able to capture the output of /proc/meminfo yet. does the system pass hardware test like memtes86 http://www.memtest86.com/ or cpuburn http://users.ev1.net/~redelm ? Switching from GNOME to KDE resolved problem. There is a meory leak in GNOME desktop. |