GNOME Bugzilla – Bug 719609
gnome-shell Memory Leak when starting and stopping the Universal Access magnifier in 3.8
Last modified: 2021-07-05 14:03:39 UTC
Starting and stopping the Universal Access magnifier causes the gnome-shell memory footprint to grow by about 200MB each time. Eventually it consumes all available RAM and results in a very sluggish system until the user logs out and back in.
Please see "Debugging GNOME Shell with valgrind" on https://wiki.gnome.org/Projects/GnomeShell/Debugging and report back.
Created attachment 263214 [details] gdb output from starting magnifier The magnifier wouldn't even start w/o it breaking into gdb.
I started the full screen magnifier in gnome and captured the attached gdb output. Let me know if you need anything else. Thanks,
(In reply to comment #3) > I started the full screen magnifier in gnome and captured the attached gdb > output. Let me know if you need anything else. > > Thanks, Pasting the trace inline makes it easier to see in case you did not yet know about that feature. (gdb) t a a bt
+ Trace 232987
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.