There has been a widely reported memory leak in the latest version of GNOME Shell which upstream GNOME have been working on fixing. While they finalise their plans and merge patches we have decided to press on with including one of the patches which should fix the biggest issues. In our testing it has proven to work well, but we’d like to get wider testing and feedback as soon as possible so we can spot any regressions before release.
It’s worth pointing out that once the patches are merged upstream, we will be issuing another update bringing us back in line with the upstream version.
You can see some of the history of this bug here:
If you’d like to help test, here’s what to do. These instructions are for amd64 based hardware, so you might need to tweak them slightly if you are using, for example, 32bit.
Just use the desktop, go about your normal business. If you feel that stability and performance are impacted by the new packages, reinstall from the ISO again and don’t install the new packages. See if it’s better on an “out of the box” install.
We’d really love to hear about any stability problems you’re having, so please contribute to the conversation on this hub post and we will closely monitor it and ask for more debugging info if we need it.
That’s great that there are attempts to patch the leak. Unfortunately, it seems that the patches provided in this post are not working on my system. My Ubuntu 18.04 is an upgrade from 17.10.
The memory consumption of the gnome-shell is still visibly increasing every time I do something where the shell action is involved. During last hour the memory gnome-shell memory consumption has increased from 175 MB to 310 MB (for example every alt-tab increases memory footprint 0.2-0.3 MB)
Haven’t seen any poor results with new packages but am wondering why you’re installing libgjs-dev with dpkg? ( most likely result is broken packages
apt would be better for this task or leave the -dev out…
Anyway, after one hour of use I do not see any regression or decline in performance. I seem to have tested a large part of the applications installed by default and no beug found at the moment.
But it’s hard to say if the system is more responsive. I have the feeling to have less peak memory consumption increase and surely the rise is more controlled. It remains difficult to evaluate
the instructions use “dpkg -iO” that should only install the debs that are already installed on the system and create no issue, are you sure you used the right command? what error are you getting?
it’s basically easier to include the -dev that way than to write “if you have libgjs-dev installed, then grab and install that extra deb otherwise the versions mismatch is going to create issues”
They were supposed to be blocked in proposed during the testing but seems like that request got overlooked well at this point I guess we can update the instructions then and ask people to simple update
have installed the latest updates and the patches. The memory drain is still there!
Every “alt+tab” increases gnome-shell’s memory usage about 0.1MB to 0.2MB.
Could those still having the issue give details on their videocard/driver/session and installed extensions? Details on how you trigger the leak/how you use the shell would also be useful.
After the update of the gnome packages this morning on the 18.04 beta version, I have lost the ability to click with the mouse. I can move the pointer but no widget answers to the click event. I can use the keyboard without problem. By the way, the click works on the gdm login screen. Do you think it has something to do with the bug correction discussed here?
Thanks, I have solved the problem by removing the .local and .cache files before restarting a new session. It did not affect other users, only the one I was logged in when updating the packets.
Question : Why is Ubuntu 18.04 shipping with a Gnome System Monitor in version 3.26 as a Snap ? I thought that the idea of Snap was to deliver more up to date Apps.
And the Snap version is slower to launch than the “real” System Monitor in version 3.28.
well at this point I guess we can update the instructions then and ask people to simple update