91ce5ca960
The object the SignalTracker belongs to is stored in a map managed by the SignalManager which keeps a reference to that object. This map is never destroyed nor is any entry ever removed. This leads to all objects that ever had SignalTrackers used on them being kept alive even after all references outside of the SignalTracker are long gone. This then also extends to other objects which are leaked indirectly through reference chains from these objects. And if some of those objects are GObjects, this will prevent them from being finalized, leaking further resources. A StWidget for example will not release its shadow textures. Fix this by destroying the SignalTracker and removing it from the SignalManager once the last signal it was tracking has been untracked. A WeakMap could have been used as well, but we need the Map to be iterable in some of the following changes. Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5807 Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5796 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2466> |
||
---|---|---|
.. | ||
config.js.in | ||
dbusUtils.js | ||
extensionUtils.js | ||
fileUtils.js | ||
gnomeSession.js | ||
history.js | ||
ibusManager.js | ||
inputMethod.js | ||
introspect.js | ||
jsParse.js | ||
keyboardManager.js | ||
loginManager.js | ||
meson.build | ||
modemManager.js | ||
objectManager.js | ||
params.js | ||
parentalControlsManager.js | ||
permissionStore.js | ||
signals.js | ||
signalTracker.js | ||
smartcardManager.js | ||
systemActions.js | ||
util.js | ||
weather.js |