I have managed to replicate it on another system, it was necessary to change the destination location away from the default in appimagelauncher for the problem to appear. I have updated the description above with detailed procedure for replicating.
There is already an open issue against appimagelauncher which is most likely related. https://github.com/TheAssassin/AppImageLauncher/issues/294 ** Description changed: + Edited description: + To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome) + 1. Install AppImageLauncher from https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and install it. If necessary run + sudo apt install -f + to fix missing dependencies. + + 2. Run it and change the appimage destination location to + ~/apps/appimages. It is necessary to change it away from the default + setting in order for the problem to appear, though probably the actual + destination is not important). Ensure that Auto start auto-integration + daemon is selected. + + 3. Download an appimage (I downloaded Cura 4.4.1 from + https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know + whether any appimage would do, probably it would. In fact I don't know + whether this step and the next need to be done at all. + + 4. Open it with appimagelauncher (this can be done by double clicking it + in nautilus) and tell it to move it and run the application. Then close + the application. + + 5. It may be necessary to reboot at this point I don't know. + + 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome- + session. It may take a few minutes to get going but then the memory + used will start increasing at several MB/minute. + + There is an issue open against appimage launcher which is likely the + same problem. + https://github.com/TheAssassin/AppImageLauncher/issues/294 + + Original description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) ** Bug watch added: github.com/TheAssassin/AppImageLauncher/issues #294 https://github.com/TheAssassin/AppImageLauncher/issues/294 ** Description changed: Edited description: To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome) 1. Install AppImageLauncher from https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and install it. If necessary run sudo apt install -f to fix missing dependencies. 2. Run it and change the appimage destination location to ~/apps/appimages. It is necessary to change it away from the default setting in order for the problem to appear, though probably the actual destination is not important). Ensure that Auto start auto-integration daemon is selected. 3. Download an appimage (I downloaded Cura 4.4.1 from https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know whether any appimage would do, probably it would. In fact I don't know whether this step and the next need to be done at all. 4. Open it with appimagelauncher (this can be done by double clicking it in nautilus) and tell it to move it and run the application. Then close the application. 5. It may be necessary to reboot at this point I don't know. - 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome- - session. It may take a few minutes to get going but then the memory - used will start increasing at several MB/minute. + 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome-shell. + It may take a few minutes to get going but then the memory used will + start increasing at several MB/minute. There is an issue open against appimage launcher which is likely the same problem. https://github.com/TheAssassin/AppImageLauncher/issues/294 Original description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862910 Title: gnome-shell leaking memory in interaction with appimagelauncher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
