Hide Forgot
Description of problem: From time to time my system becomes substantially unuseable for tens of seconds at a time. It is swapping. I have 4GB RAM. I am running a GNOME desktop and I'm a heavy user, sure. Historically, the problem "goes away" if I logout or I reboot. It is super-convenient for me to never logout and never reboot for months at a time. This is my desktop machine. I have identified gnome-panel as a culprit here in the memory use. My gnome-panel is 1.6GB and the system is bogging down with memory contention among firefox, thunderbird, nautilus and gwibber. This report is about characterizing gnome-panel. Version-Release number of selected component (if applicable): $ rpm -q gnome-panel gnome-panel-2.30.0-4.fc13.i686 How reproducible: Tn general yes. It takes days or weeks, but sometimes less, to get it to this state. Steps to Reproduce: 1. login 2. do work ... sleep, eat ... rinse repeat 3. (never log out) Actual results: ps -ef | grep gnome-panel (see the process size) Expected results: Keep it to ~200MB? Additional info: Representations of the current state ... $ ps -ef | grep gnome-panel wbaker 22309 22073 0 2010 ? 00:31:43 gnome-panel --sm-client-id 1010eaf64f6a8dd0f9128356862071974500000265000048 wbaker 25528 25353 0 11:10 pts/4 00:00:00 grep gnome-panel $ ps -lp 22309 | grep gnome-panel 0 S 500 22309 22073 0 80 0 - 425001 poll_s ? 00:31:43 gnome-panel $ bc 425001*4096/1024^3 1 scale=6 425001*4096/1024^3 1.621250 That's 1.6GB What else is going on here? top - 11:15:29 up 64 days, 15:41, 9 users, load average: 0.88, 1.70, 1.49 Tasks: 400 total, 3 running, 396 sleeping, 0 stopped, 1 zombie Cpu(s): 25.9%us, 2.3%sy, 0.0%ni, 71.0%id, 0.7%wa, 0.0%hi, 0.1%si, 0.0%st Mem: 4112972k total, 3676776k used, 436196k free, 18000k buffers Swap: 8290300k total, 2211728k used, 6078572k free, 1273916k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 17213 wbaker 20 0 311m 44m 9612 S 44.4 1.1 37:41.94 npviewer.bin 22412 wbaker 20 0 330m 25m 6900 R 30.8 0.6 531:48.25 pidgin 16995 wbaker 20 0 1442m 696m 16m S 23.2 17.3 186:02.00 firefox 21363 root 20 0 236m 70m 11m S 10.6 1.8 4560:23 Xorg 12724 wbaker 20 0 245m 9340 3028 S 4.6 0.2 67:31.02 npviewer.bin 22307 wbaker 20 0 231m 10m 9808 S 1.3 0.3 108:51.06 pulseaudio 9673 wbaker 20 0 520m 50m 6832 S 0.7 1.3 8:15.16 nautilus 22013 wbaker 20 0 390m 70m 3192 S 0.7 1.8 29:08.05 gedit 22301 wbaker 20 0 160m 16m 2176 S 0.7 0.4 24:53.20 gnome-settings- 22309 wbaker 20 0 1660m 74m 4876 S 0.7 1.9 31:46.49 gnome-panel 25648 wbaker 20 0 2876 1216 808 R 0.7 0.0 0:00.69 top 31800 wbaker 20 0 170m 7196 4224 S 0.7 0.2 3:09.47 gnome-terminal 5789 wbaker 20 0 181m 11m 3044 S 0.3 0.3 4:13.71 evince 7037 wbaker 20 0 190m 7308 2056 S 0.3 0.2 4:09.29 evince 15345 wbaker 20 0 178m 22m 3152 S 0.3 0.6 0:48.37 evince focus on the gnome-panel (the "9 users" are all me) An "adequate" workaround here would be a recipe for killing off the gnome panel and restarting a new one that didn't destroy the ongoing login session. ~/.xsession-errors is too large to show; there is no smoking gun here. Just lots and lots of those Gtk assertion and warning messages that fail in all the Gtk applications. Evince spews horrendous amounts of issues when it doesn't like character sets; NSPluginViewer ... etc. My point is that there are no obvious warning or error messages from gnome-panel that would indicate why it is unhappy and leaking. $ ls -las ~/.xsession-errors 1516492 -rw-------. 1 wbaker wbaker 1552880233 Feb 3 11:23 /home/wbaker/.xsession-errors $ ls -lash ~/.xsession-errors 1.5G -rw-------. 1 wbaker wbaker 1.5G Feb 3 11:23 /home/wbaker/.xsession-errors
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.