Gnome shell memleaks?

Message

jelf · Post by **jelf** » Tue Jul 01, 2014 11:03 pm

Hello.
I'm using "GNOME Shell 3.10.4" with "x11-drivers/nvidia-drivers-337.25". I neither use any extensions (according to "eselect gnome-shell-extensions") nor manualy installed them, so it seems to memory leak in gnome shell, becose it uses less then 1G memory on startup, but more then 2.6G after a day of work (when all windows are closed). It also use much processor time at this moments. I do not sure this is a memory leak, but have no other ideas how to explain this.
This problem is most often seen after playing video games via wine or watching video via vlc. I don't know, what information i should attach, if there isn't a common problem. However i will attach make.conf, just in case this problem is about use flags
PS should i select only nvidia in my VIDEO_CARDS, or it is better to save nouveau there too?
PPS i am using amd64

Make.conf: http://pastebin.com/n64sKb7c

Solved: using systemd fixed all possibly leaks (didn't tested with system monitor extension)

russK · Post by **russK** » Wed Jul 02, 2014 1:05 am

I think you might be on to something, it looks like I may have the same issue, I just never noticed because I have much more memory than I need.

I noticed just now that you can use 'gnome-shell -r' (replace) which will start a new process and kick the old one out. It's mildly disruptive but the memory footprint goes back down to what it was when first started.

mackal · Post by **mackal** » Wed Jul 02, 2014 1:09 am

You can also hit Alt+F2 and type r to restart gnome-shell. I have also noticed it uses a lot of memory but I also have too much RAM

jelf · Post by **jelf** » Wed Jul 02, 2014 1:45 am

russK wrote:I think you might be on to something, it looks like I may have the same issue, I just never noticed because I have much more memory than I need.

I noticed just now that you can use 'gnome-shell -r' (replace) which will start a new process and kick the old one out. It's mildly disruptive but the memory footprint goes back down to what it was when first started.

It works, and works better, then xdm restart

. Thank you a lot

greyspoke · Post by **greyspoke** » Wed Jul 02, 2014 9:59 am

This was discussed on this thread here.

There is a Gnome bug about it (in addition to the link I posted back there) here. Though it is not clear that Gnome recognise them as bugs from the comments by the devs on that.

jelf · Post by **jelf** » Wed Jul 02, 2014 12:18 pm

greyspoke wrote:This was discussed on this thread here.

There is a Gnome bug about it (in addition to the link I posted back there) here. Though it is not clear that Gnome recognise them as bugs from the comments by the devs on that.

Ouch, it seems not to be solvable by masking/unmasking

Interesting that i never noticed this on previous system

Thistled · Post by **Thistled** » Wed Jul 02, 2014 12:44 pm

Yep, it's been doing this for about a year on my box.

If you enable the system monitor extension you will lose RAM in no time at all.
Without the system monitor enabled, you will lose RAM over a longer period of time.

When you only have 4Gb of RAM, you notice this in no time at all.

As suggested above Alt+F2 followed by r will restore the RAM.

I did notice when the memory mappings (or whatever it's called) are checked, there is a dump file which is swallowing the RAM.

This has been around for a while, and I don't know why it has not been addressed.
Perhaps it's unique to Gentoo, and that is why it is taking so long.

If I could code I would help out. But alas.

jelf · Post by **jelf** » Wed Jul 02, 2014 8:08 pm

Thistled wrote:Yep, it's been doing this for about a year on my box.

If you enable the system monitor extension you will lose RAM in no time at all.
Without the system monitor enabled, you will lose RAM over a longer period of time.

When you only have 4Gb of RAM, you notice this in no time at all.

As suggested above Alt+F2 followed by r will restore the RAM.

I did notice when the memory mappings (or whatever it's called) are checked, there is a dump file which is swallowing the RAM.

This has been around for a while, and I don't know why it has not been addressed.
Perhaps it's unique to Gentoo, and that is why it is taking so long.

If I could code I would help out. But alas.

Can you tell me more about that file? Where was it located? I hope to find solution in gnome configuration files / just in sources using "find"

Thistled · Post by **Thistled** » Thu Jul 03, 2014 3:16 pm

Sure Jelf.

Open Gnome-system-monitor
Right click on "gnome-shell"
Select "Memory Maps"

It will display all the processes using memory for Gnome Shell.

In my case, the file in question had "dump" in the title and was consuming memory every fews seconds.

Hope this helps.

jelf · Post by **jelf** » Thu Jul 03, 2014 3:30 pm

Thistled, i do not have "dump" file there. Sure about that.
Anyway, thank you for this method, i'd never used it before, but it may be usefull

Thistled · Post by **Thistled** » Thu Jul 03, 2014 4:29 pm

Okay Jelf.

If you were to enable the system monitor extension then I guess you would see the dump file.

If you carefully scan the "memory map" for gnome-shell, you should be able to see which process
is gradually consuming the memory.

Hope this helps.

jelf · Post by **jelf** » Fri Aug 08, 2014 6:54 am

Okay, i have the solution: never use desktop/gnome profile, only desktop/gnome/systemd. Damn