Description of problem: My laptop was frozen for a minute. After that the gnome-shell daemon restarted it self. Version-Release number of selected component: gnome-shell-3.6.2-6.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: getNext executable: /usr/bin/gnome-shell kernel: 3.7.2-204.fc18.x86_64 remote_result: 737709 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 getNext at jsgc.h:651 #1 NewFinalizableGCThing<JSObject> at jsgcinlines.h:122 #2 js_NewGCObject at jsgcinlines.h:139 #3 NewObject<false, false> at jsobjinlines.h:1081 #4 NewArray<true> at jsarray.cpp:3060 #5 js::NewDenseCopiedArray at jsarray.cpp:3093 #6 gjs_invoke_c_function at gi/function.c:1160 #7 function_call at gi/function.c:1204 #8 CallJSNative at jscntxtinlines.h:701 #9 js::Invoke at jsinterp.cpp:696 Potential duplicate: bug 737709
Created attachment 685363 [details] File: backtrace
Created attachment 685364 [details] File: build_ids
Created attachment 685365 [details] File: cgroup
Created attachment 685366 [details] File: core_backtrace
Created attachment 685367 [details] File: dso_list
Created attachment 685368 [details] File: environ
Created attachment 685369 [details] File: limits
Created attachment 685370 [details] File: maps
Created attachment 685371 [details] File: open_fds
Created attachment 685372 [details] File: proc_pid_status
Created attachment 685373 [details] File: var_log_messages
I see the same backtrace suffix in a bug against elinks. This looks more likely as a bug in js...
*** Bug 906828 has been marked as a duplicate of this bug. ***
How it can be reproduced?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.