Closed genodeftest closed 5 years ago
It seems like these lines from syslog belong to the stacktraces above:
Object .Gjs_ProcessItemsContainer (0x55c14b605390), has been already finalized. Impossible to set any property to it.
Object .Gjs_DirectoriesContainer (0x55c14d0e8560), has been already finalized. Impossible to set any property to it.
Object .Gjs_NetworkInterfaceItemsContainer (0x55c14e3cef00), has been already finalized. Impossible to set any property to it.
Object .Gjs_SystemLoadItemsContainer (0x55c14c3ee4e0), has been already finalized. Impossible to set any property to it.
This is basically the same as issue https://github.com/elvetemedve/gnome-shell-extension-system-monitor/issues/46.
Some of these has been fixed in version 14, so I'm closing this and keep the other related issue open.
Steps to reproduce: unclear.
What happens: When running gnome-shell, the org.gnome.Shell.desktop ID logs these stack traces to syslog quite often:
and there is also a longer version. These stack traces come in bursts, usually of 5 or 10 at once (same second according to syslog).
What should happen: No stacktrace.
Additional info: Printing these stacktraces is a feature introduced in or after 3.26.0 release, afaik. See also: sustmi/gnome-shell-extension-windowoverlay-icons#4 and https://gitlab.gnome.org/GNOME/gnome-shell/issues/11.
It is unclear to me why those stacktraces are thrown. They might be indicating that the object has already been destroyed somewhere else or that it cannot be destroyed because it is still being referenced by from somewhere else.
Please note that I did not disable this extension at all and I don't know why this function gets called. I guess that it is being called on screen lock or suspend.
Installed software versions: gnome-shell-3.26.2-4.fc27.x86_64 gjs-1.50.4-1.fc27.x86_64 mutter-3.26.2-2.fc27.x86_64