The patch fixes a leak that triggers when using text shadows in shell widgets
such as StLabel.
At least in noble (GNOME 46), I do not see any text shadows when using the
WhiteSur-Light shell theme.
Indeed, attaching GDB to gnome-shell and setting up the following breakpoint:
break _st_create_shadow_pipeline_from_actor if
$_caller_is("st_label_paint")
I cannot trigger the breakpoint with any shell interaction.
If I edit the gnome-shell.css to include something like:
#panel .clock {
text-shadow: 0 1px 3px 3px rgba(0, 0, 0, 0.35) !important;
}
The I see a text shadow on the clock, and the breakpoint is triggered with
every passing minute when the clock updates.
But even then, I do not get *any* memory usage increase by repeatedly adjusting
the clock.
So I'm quite skeptical of this bug and/or verification plan, for noble
at least.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2121786
Title:
Using a custom theme leaks 10-15 MB per hour
Status in GNOME Shell:
Fix Released
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Noble:
In Progress
Status in gnome-shell source package in Plucky:
Fix Committed
Bug description:
[ Impact ]
gnome-shell has a memory leak, which causes the user's memory to be
gradually consumed after several days of gnome-shell being open with
some themes, even when no actual user-visible tasks are being
performed.
[ Test Plan ]
1. Install the White Sur theme from
https://github.com/vinceliuice/WhiteSur-gtk-theme
2. Enable the theme in Gnome Tweaks.
3. Start tracking memory usage in a format that can be easily graphed.
Include any data and graphing scripts used in your tests in this report.
4. Keep gnome-shell open for 2 days, and keep the machine idle
5. Save graph of memory usage
Perform these steps on both an unpatched system and a patched system
and compare the results.
[ Expected Behavior ]
Memory utilization graph should be relatively flat at start and end of
experiment
[ Actual Behavior ]
Memory utilization graph increases roughly linearly with respect to
time
[ Where problems could occur ]
This patch changes which memory management primitive is used in one
place, which could theoretically result in a user-visible crash if
improperly implemented.
[ Other info ]
This is to track upstream bug:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8509
which seems to be a regression starting in gnome-shell 46.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2121786/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
