You are not logged in.

#1 2017-01-17 12:34:02

Bulbomesh
Member
Registered: 2017-01-16
Posts: 1

Gnome shell 3.22.2 + GDM 3.22.1 : Memory leaks.

In 5 hours of uptime with the standart workflow the gnome-shell goes from ~100MB to ~300MB and starts to lag. Changing the display manager solves the problem, but I really like gdm, so I'm looking for another solution. Is there anything I can do?
One thing I've noticed: Every time I change the focused application with alt+tab it takes an additional MB of memory.

Offline

#2 2017-01-23 11:21:02

flortsch
Member
From: Linz, Austria
Registered: 2015-07-21
Posts: 39
Website

Re: Gnome shell 3.22.2 + GDM 3.22.1 : Memory leaks.

Report the error upstream if not already existing (https://bugzilla.gnome.org).
In the meanwhile, you could try to run GDM and Gnome Shell in traditional X11 Session.

Last edited by flortsch (2017-01-23 11:21:42)

Offline

#3 2017-03-14 10:25:43

hussam
Member
Registered: 2006-03-26
Posts: 572
Website

Re: Gnome shell 3.22.2 + GDM 3.22.1 : Memory leaks.

First of all, sorry for posting in an old thread.
I did some statistics on Gnome 3.23.92 (on a skylake corei5 with 8GB ram).

I wrote a cron job that tests the memory usage of gnome-shell process in an X11 session. The script runs once a minute and if the VmRSS counter goes about 500MB, it reads session data (DBUS_SESSION_BUS_ADDRESS, DISPLAY, etc...) and reexecutes gnome-shell (which takes a whole second in itself). It then increments a counter in /tmp/reexecutioncounter.

So far it ran 23 times in 40 hours of uptime. This means every 104 minutes.
Without the leaks, gnome-shell would use around 300MB after initial memory allocations.

This means a leak of ~200MB every 104 minutes.
A full day contains 1440 minutes. This means around 2692MB (~2.63GB) of ram leaked per 24 hours.

Last edited by hussam (2017-03-14 10:28:17)

Online

#4 2017-03-14 16:10:51

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: Gnome shell 3.22.2 + GDM 3.22.1 : Memory leaks.

Its not old, just ripe smile   Is the shell just idling? or is it processing any other jobs?  You might want to grab the output of systemctl status just before you restart the shell.  Might provide some more insight.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2017-03-14 16:34:43

hussam
Member
Registered: 2006-03-26
Posts: 572
Website

Re: Gnome shell 3.22.2 + GDM 3.22.1 : Memory leaks.

As far as I have noticed, the leaks have three main reasons:
1) Clicking Applications then "Show Applications". This adds around 2 to 4MB of memory and not freed afterwards. I guess this is consumed to display all the .desktop file icons.
2) Locking the screen. It continuously eats more memory when the arrow at the bottom of the curtain is animated. This is a large leak.
3) Moving windows around eats some memory. Maximizing some does too.

I've submitted multiple valgrind logs upstream. It appears most of the issues are in the mutter bundled version of cogl and mozjs.

While GTK+ itself is in a very good position at the moment (GTK3 is in feature freeze and GTK4 won't be released for two more years), I wish developers would find time to investigate and address Gnome-shell/mutter issues.

I also recompiled mesa with debug information and tested. The valgrind logs where similar to the ones generated while using NVIDIA proprietary driver apart from one detail. NVIDIA complains a bit more while exiting gnome-shell and contains no debug symbols.

I'll edit my post and attach the systemctl status output.

Last edited by hussam (2017-03-14 16:38:42)

Online

Board footer

Powered by FluxBB