Version-Release number of selected component: gnome-shell-3.11.3-1.fc21 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: js_free executable: /usr/bin/gnome-shell kernel: 3.13.0-0.rc8.git0.1.fc21.x86_64+debug runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 js_free at dist/include/js/Utility.h:174 #2 free_ at dist/include/js/Utility.h:613 #5 finish at /usr/src/debug/mozjs17.0.0/js/src/jsobjinlines.h:881 #6 finalize at /usr/src/debug/mozjs17.0.0/js/src/jsobjinlines.h:238 #7 finalize<JSObject> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:355 #8 FinalizeTypedArenas<JSObject> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:419 #9 js::gc::FinalizeArenas(js::FreeOp *, js::gc::ArenaHeader **, js::gc::ArenaList &, enum js::gc::AllocKind, js::SliceBudget &) at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:456 #10 backgroundFinalize at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:1686 #11 js::SweepBackgroundThings at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:2842 #12 js::GCHelperThread::doSweep at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3116 Potential duplicate: bug 1040951
Created attachment 849947 [details] File: backtrace
Created attachment 849948 [details] File: cgroup
Created attachment 849949 [details] File: core_backtrace
Created attachment 849950 [details] File: dso_list
Created attachment 849951 [details] File: environ
Created attachment 849952 [details] File: exploitable
Created attachment 849953 [details] File: limits
Created attachment 849954 [details] File: maps
Created attachment 849955 [details] File: open_fds
Created attachment 849956 [details] File: proc_pid_status
Created attachment 849957 [details] File: var_log_messages
More js:: stuff... desktop team, hello? we have GNOME crashing left right and centre in f20 and rawhide and it doesn't seem like there's much movement on any of the bugs?
https://bugzilla.redhat.com/show_bug.cgi?id=js-shape-finalize is the bug I've been duping all the js:: crashes off against. owen says: <owen> adamw: the js crashes are some sort of memory corruption issue, and aren't going to be debuggable without a high quality valgrind log or a triggerable-at-will reproducer in the hands of a developer <owen> adamw: That is, the backtrace at time of crash is unlikely to provide a useful clue
*** This bug has been marked as a duplicate of bug 1034467 ***