Control: clone 1034356 -2 Control: forwarded 1034356 https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/832 Control: reassign 1034356 libgjs0g 1.74.2-1 Control: fixed 1034356 1.76.1-1 Control: reassign -2 gnome-shell-extension-vertical-overview Control: retitle -2 gnome-shell-extension-vertical-overview: Attempting to call back into JSAPI during the sweeping phase of GC Control: affects 1034356 = gnome-shell Control: affects -2 = gnome-shell
H.-Dirk Schmitt wrote: > After migration to bookworm on 2 different machines the gnome-shell was > frozen in the last week. > Via SSH – or switching to the good old console – I was able to see that > journald was running with 100% cpu at that time. ... > But I found 2 valuable hints that the issue can be mitigated with an > upgrade of gjs to 1.76.1 > - https://github.com/pop-os/pop/issues/2893 > - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 Because the log flooding and UI freeze is the more serious part of this issue, I'm cloning the bug and using the original bug number #1034356 to represent the log flooding and UI freeze. Any time "Attempting to call back into JSAPI during the sweeping phase of GC" appears in the log, that indicates a bug in either the Shell or an extension (in this case I think it's most likely to be the vertical-overview extension). Please use the cloned bug number (which will be higher than #1034356) to represent this. The key change in gjs seems to be the second commit of <https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/832> so I'll try to build a package with that change for testing. > > I see from the log messages that you have a non-default theme and > > several > > Shell extensions enabled. Can this be reproduced without any > > extensions? > > The machines with problems are administered remotely – so I can't > disable extensions et.al. Sorry, there is a limit to what the GNOME team can do to help you if it is not possible to debug an issue. smcv