Starting/Stopping tasks produces lots of log messages and sometimes fails
Closed this issue · 1 comments
xrayn commented
Clicking on Task Start or Stop generates some weird entries in the journal logfile.
At the moment, tasks are started and stopped correctly. but earlier it happened that this did not work until I reloaded the extension. I could not reproduce it since.
My System is Arch
GNOME Shell 40.1
Package: gnome-shell 1:40.0+78+g954131c1c-1
May 11 10:55:12 lunar gnome-shell[1847]: Object St.BoxLayout (0x55ffdf12b990), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
May 11 10:55:12 lunar gnome-shell[1847]: clutter_actor_destroy_all_children: assertion 'CLUTTER_IS_ACTOR (self)' failed
May 11 10:55:12 lunar gnome-shell[1847]: == Stack trace for context 0x55ffdcb0d120 ==
May 11 10:55:12 lunar gnome-shell[1847]: #0 55ffe8851bf8 i /home/gg/.local/share/gnome-shell/extensions/taskwhisperer-extension@infinicode.de/components/flatList/flatList.js:45 (35fdc4767b50 @ 22)
May 11 10:55:12 lunar gnome-shell[1847]: #1 7ffc89ed3b50 b /home/gg/.local/share/gnome-shell/extensions/taskwhisperer-extension@infinicode.de/components/screens/taskOverviewScreen/taskOverviewScreen.js:138 (35fdc4767240 @ 460)
May 11 10:55:12 lunar gnome-shell[1847]: #2 7ffc89ed3be0 b self-hosted:693 (35fdc4773d80 @ 15)
...
cinatic commented
thanks for the report it is indeed a severe stupid issue as it can cause refresh cycles and high cpu usage, caused by not explicitly unregister the previous refresh timer, will be fixed in the next version