Since upgrading to F15 (x86_64, current with all updates and updates-testing), I've noticed once in a while that my desktop is particularly slow to perform window operations (move, iconify, maximize, quit with the X button in the title bar, etc.), and logging out and logging back in seems to clear up the problem. I think I've figured out why -- gnome-shell appears to be leaking memory like a sieve. Earlier today when things were particularly slow, I checked, and System Monitor reported that gnome-shell was consuming 1.0 GiB of memory. Wow! I restarted, and it dropped to about 40 MiB of memory and then immediately started to grow. I thought that maybe the extensions I was using (Dock and Weather) were the issue, so I restarted again,and this time it started at about 27 MiB, but again it immediately started to grow. Now, a few hours later, it's up from 27 MiB to 207.8 MiB, and for most of that time I wasn't even using my computer! Something needs to be done about this...
I've noticed the memory gradually creeping up as well. You don't have to log out, just restart gnome shell with Alt-F2, press "r", Enter.
Experiencing same issue in F16 TC2 fully upgraded system also, i386. within 7 hrs, it jumped from some 40MB to 430 MB ! Also happening when number of unseen notifications are increasing alot in the system panel. Doing a Alt+F2 and 'r' does bring it back to sane levels, but some serious memory leak appears to be happening.
First rule of bug reporting: mention the version of whatever it is that you are complaining about.
Matthias, I told you in my initial bug report exactly what version I'm using, and the problem has persisted in every single F15 or F16 upgrade I've done since then. There are many reports all over the internet about this issue. It's not esoteric or difficult to reproduce.
Thanks for the tip Matthias. I think its a gnome-shell issue, so mentioning its version as reported by rpm -qa.. gnome-shell-3.2.1-1.fc16.i686 If any other info is needed, do let us know.
With gnome-shell-3.2.1-1.fc16.x86_64, gnome-shell in ps shows VSZ=1242620 and RSS=60412 before Alt-F2 r, when it has been running for less than 5 hours. Immediately after Alt-F2 r, it shows VSZ=331484 and RSZ=6108.
I don't know if this is the same bug or not because I've only encountered it with recent Rawhide, but gnome-shell does indeed have memory leak problems. After a few hours: corbet 1163 0.8 13.6 2420996 1097052 ? Sl Apr04 8:35 /usr/bin/gnome-shell That will continue to grow indefinitely until the OOM killer makes an unwelcome appearance. In fact, over the time it took to write this it has gone to: corbet 1163 0.8 13.7 2433776 1109716 ? Sl Apr04 8:41 /usr/bin/gnome-shell I'm currently running: gnome-shell-3.3.90-2.fc17.x86_64 clutter-1.10.0-2.fc18.x86_64 mutter-3.3.90-2.fc17.x86_64 I have no extensions installed. Please let me know if there's any other information I can provide.
(In reply to comment #7) > I don't know if this is the same bug or not because I've only encountered it > with recent Rawhide, but gnome-shell does indeed have memory leak problems. > After a few hours: > > corbet 1163 0.8 13.6 2420996 1097052 ? Sl Apr04 8:35 > /usr/bin/gnome-shell > > That will continue to grow indefinitely until the OOM killer makes an unwelcome > appearance. In fact, over the time it took to write this it has gone to: > > corbet 1163 0.8 13.7 2433776 1109716 ? Sl Apr04 8:41 > /usr/bin/gnome-shell > > I'm currently running: > > gnome-shell-3.3.90-2.fc17.x86_64 > clutter-1.10.0-2.fc18.x86_64 > mutter-3.3.90-2.fc17.x86_64 > > I have no extensions installed. Please let me know if there's any other > information I can provide. There were some bug fixes between 3.3.90 and 3.4.0, so that would be my first guess. I'm told that once the mega-gnome-3.4 update https://admin.fedoraproject.org/updates/FEDORA-2012-4879 is pushed to stable it will also be inherited by F18.
OK, it does appear that 3.4.0 has closed up the leak on my system. Been running for a couple of days, and no OOM killer appearances yet. That makes me a lot happier, thanks.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.