Tried to get a Massif profile, starting a new gnome-shell with --replace, but it fails before it can replace the running process due to bug #1700465:
$ valgrind --tool=massif --num-callers=32 --log-file=/tmp/gnome- shell.valgrind.log gnome-shell --replace (gnome-shell:30065): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory If we can't replace it, it should be possible to get the display manager to launch gnome-shell in valgrind at login. The order of execution seems to be: gdm3 -> gdm-session-worker -> gdm-wayland-session -> gnome-session-binary -> gnome-shell. I hit a dead end when trying to find config files though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
