It appears the mozjs Heap is a bogus pointer from very early on.
Next steps:
1. See if the latest gjs update has changed the situation (waiting on new live images).
2. Look into gjs to see if the problem starts in there or if the whole gjs context from gnome-shell is invalid.
It appears the mozjs Heap is a bogus pointer from very early on.
Next steps:
1. See if the latest gjs update has changed the situation (waiting on new live images).
2. Look into gjs to see if the problem starts in there or if the whole gjs context from gnome-shell is invalid.