GNOME Bugzilla – Bug 782060
Crash after running sushi two times
Last modified: 2017-05-06 06:39:15 UTC
Created attachment 350864 [details] journal of systemd gnome-shell crashes with following messages in log: 10:28:44 org.gnome.Shell.desktop[404]: ** 10:28:44 org.gnome.Shell.desktop[404]: Gjs:ERROR:./gjs/jsapi-util-root.h:317:void GjsMaybeOwned<T>::trace(JSTracer*, const char*) [with T = JS::Value]: assertion failed: (!m_rooted) Steps to reproduce: 1. Open Nautilus window; 2. Select some object and press <Space> for running sushi; 3. Press <Space> for closing sushi window; 4. Press <Space> for running sushi again; 5. Wait about 10-30 seconds; OS: Archlinux gnome-shell 3.24.1+2+g45c2627d4-1 sushi 3.24.0-1 js38 38.8.0-3 gjs 1.48.2-1
The stack points to an assertion in GJS' garbage collection, so tentatively reassigning to gjs.
Stack trace printed here, for convenience: Stack trace of thread 404: #0 0x00007f2b5018fa10 raise (libc.so.6) #1 0x00007f2b5019113a abort (libc.so.6) #2 0x00007f2b5078f465 g_assertion_message (libglib-2.0.so.0) #3 0x00007f2b5078f4fa g_assertion_message_expr (libglib-2.0.so.0) #4 0x00007f2b526552a4 n/a (libgjs.so.0) #5 0x00007f2b4b53cf6d n/a (libmozjs-38.so) #6 0x00007f2b4b5195cd n/a (libmozjs-38.so) #7 0x00007f2b4b870e90 n/a (libmozjs-38.so) #8 0x00007f2b4b89cede n/a (libmozjs-38.so) #9 0x00007f2b4b89d8c0 n/a (libmozjs-38.so) #10 0x00007f2b4b89db0d n/a (libmozjs-38.so) #11 0x00007f2b4b89ded4 n/a (libmozjs-38.so) #12 0x00007f2b5266eee9 gjs_schedule_gc_if_needed (libgjs.so.0) #13 0x00007f2b5266ef54 gjs_call_function_value (libgjs.so.0) #14 0x00007f2b5264a0a5 gjs_closure_invoke (libgjs.so.0) #15 0x00007f2b52661dcc n/a (libgjs.so.0) #16 0x00007f2b50a41f75 g_closure_invoke (libgobject-2.0.so.0) #17 0x00007f2b50a53f82 n/a (libgobject-2.0.so.0) #18 0x00007f2b50a5cbdc g_signal_emit_valist (libgobject-2.0.so.0) #19 0x00007f2b50a5cfbf g_signal_emit (libgobject-2.0.so.0) #20 0x00007f2b51f3286a meta_stack_tracker_sync_stack (libmutter-0.so.0) #21 0x00007f2b51f328b9 n/a (libmutter-0.so.0) #22 0x00007f2b51f33953 n/a (libmutter-0.so.0) #23 0x00007f2b512bcd34 n/a (libmutter-clutter-0.so) #24 0x00007f2b512bd9e7 n/a (libmutter-clutter-0.so) #25 0x00007f2b507687b7 g_main_context_dispatch (libglib-2.0.so.0) #26 0x00007f2b50768a20 n/a (libglib-2.0.so.0) #27 0x00007f2b50768d42 g_main_loop_run (libglib-2.0.so.0) #28 0x00007f2b51f27d0c meta_run (libmutter-0.so.0) #29 0x0000000000401ff7 main (gnome-shell) #30 0x00007f2b5017c511 __libc_start_main (libc.so.6) #31 0x000000000040212a n/a (gnome-shell) I'll try to reproduce this, but can you by any chance get a stack trace with debug symbols?
I'm going to assume this is another manifestation of the same crash as bug 781799, since both stack traces seem to occur when someone is suffering from it. *** This bug has been marked as a duplicate of bug 781799 ***