After further testing I find the following in the logs at the approximate time of crash:
gnome-shell[4057]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Apr 20 09:37:27 gnome-shell[4057]: The offending callback was SourceFunc().
I have also seen a lot of these messages although it isn't clear to me if they are related:
nome-shell[4057]: == Stack trace for context 0x5620be49a900 ==
gnome-shell[4057]: The offending callback was set_actor(), a vfunc.
gnome-shell[4057]: Error adding children to desktop: Not enough place at monitor 0
gnome-shell[4057]: message repeated 49 times: [ Error adding children to desktop: Not enough place at monitor 0]
Perhaps this will be helpful in finding the cause of the crash.
After further testing I find the following in the logs at the approximate time of crash:
gnome-shell[4057]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Apr 20 09:37:27 gnome-shell[4057]: The offending callback was SourceFunc().
I have also seen a lot of these messages although it isn't clear to me if they are related:
nome-shell[4057]: == Stack trace for context 0x5620be49a900 ==
gnome-shell[4057]: The offending callback was set_actor(), a vfunc.
gnome-shell[4057]: Error adding children to desktop: Not enough place at monitor 0
gnome-shell[4057]: message repeated 49 times: [ Error adding children to desktop: Not enough place at monitor 0]
Perhaps this will be helpful in finding the cause of the crash.