Bug 56220
Summary: | 2.4.9-13 memory usage explodes and uses swap until most memory is consumed. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jim Wray <wray> | ||||
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.2 | CC: | rhbz | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2003-06-07 20:46:59 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: | |||||||
Attachments: |
|
Description
Jim Wray
2001-11-14 00:02:58 UTC
can you use "top" and then the "M" key to see if there's no accidental userspace memory leak ? (M sorts by memory usage) Created attachment 37622 [details]
a screenshot of top
I have attached a screenshot of top. It looks like it is a memory leak of some sort. Upon launch, galeon spawns 5 galeon-bin processes each taking 9% or 46M of memory. Additionally, I guess when I went to a certain page, 17 java_vm processes were launched, each taking 5% or 25M of memory. This constitutes 655M of memory usage! While this much memory use is appalling, when closing the applications down, the swap and memory usage still remains high, meaning there must be a memory leak of some sort. I know you don't distribute the jdk, and I am using galeon 12.7, so this is certainly not RH's responsibility, but, it looks like the mozilla, folks and galeon people need to work on this issue pretty badly. Thanks for your help, and any suggestions you might still have. But, I would have to say that although I didn't experience the grind down problems in 7.1, this probably isn't a kernel issue as much as memory issue with either mozilla's rendering engine used in galeon, or galeon itself coupled with how many java_vm's are launched each using 25M of memory. ouch! Thanks. |