Activity log for bug #1862910

Date Who What changed Old value New value Message
2020-02-12 08:59:16 Colin Law bug added bug
2020-02-12 12:06:53 Daniel van Vugt gnome-shell (Ubuntu): status New Incomplete
2020-02-12 12:08:06 Daniel van Vugt bug added subscriber Daniel van Vugt
2020-02-12 14:21:57 Colin Law attachment added Desktop screenshot https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327658/+files/Screenshot%20from%202020-02-12%2014-02-37.png
2020-02-12 14:23:30 Colin Law attachment added lspci -k https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327669/+files/lspcik.txt
2020-02-12 14:24:45 Colin Law attachment added glxinfo.txt https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+attachment/5327670/+files/glxinfo.txt
2020-02-13 03:20:22 Daniel van Vugt bug watch added https://gitlab.gnome.org/GNOME/gnome-shell/issues/2085
2020-02-13 03:20:39 Daniel van Vugt bug watch removed https://gitlab.gnome.org/GNOME/gnome-shell/issues/2085
2020-02-13 20:19:50 Colin Law summary gnome-shell leaking memory gnome-shell leaking memory in interaction with appimagelauncher
2020-02-13 20:36:37 Colin Law 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) 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)
2020-02-13 20:39:16 Colin Law bug watch added https://github.com/TheAssassin/AppImageLauncher/issues/294
2020-02-13 20:41:12 Colin Law description 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) 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-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)
2020-02-13 20:41:24 Colin Law gnome-shell (Ubuntu): status Incomplete New
2020-02-14 02:13:56 Daniel van Vugt summary gnome-shell leaking memory in interaction with appimagelauncher gnome-shell leaking memory when a customized AppImageLauncher is running
2020-02-14 02:13:59 Daniel van Vugt gnome-shell (Ubuntu): importance Undecided Medium
2020-02-14 02:14:08 Daniel van Vugt tags amd64 apport-bug eoan amd64 apport-bug eoan leak
2020-02-14 02:16:09 Daniel van Vugt gnome-shell (Ubuntu): importance Medium Low
2020-02-17 16:48:10 Colin Law bug watch added https://github.com/TheAssassin/AppImageLauncher/issues/301
2020-02-18 01:35:59 Daniel van Vugt bug task added appimagelauncher
2020-02-18 01:36:14 Daniel van Vugt bug task deleted appimagelauncher
2020-03-08 23:33:36 Launchpad Janitor gnome-shell (Ubuntu): status New Confirmed
2020-05-14 08:13:45 Daniel van Vugt tags amd64 apport-bug eoan leak amd64 apport-bug eoan gnome-shell-leak
2020-08-11 09:57:21 Daniel van Vugt gnome-shell (Ubuntu): status Confirmed Won't Fix