Version-Release number of selected component: gjs-1.37.6-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c 'const Main = imports.main; Main.start();' --no-default-window crash_function: object_instance_finalize executable: /usr/bin/gjs-console kernel: 3.11.1-300.fc20.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 object_instance_finalize at gi/object.c:1331 #3 finalize at /usr/src/debug/mozjs17.0.0/js/src/jsobjinlines.h:235 #4 finalize<JSObject> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:355 #5 FinalizeTypedArenas<JSObject> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:419 #6 js::gc::FinalizeArenas at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:456 #7 finalizeNow at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:1634 #8 js::gc::ArenaLists::queueObjectsForSweep at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:1730 #9 BeginSweepPhase at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3759 #10 IncrementalCollectSlice at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4230 #11 GCCycle at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4408
Created attachment 802123 [details] File: backtrace
Created attachment 802124 [details] File: cgroup
Created attachment 802125 [details] File: core_backtrace
Created attachment 802126 [details] File: dso_list
Created attachment 802127 [details] File: environ
Created attachment 802128 [details] File: limits
Created attachment 802129 [details] File: maps
Created attachment 802130 [details] File: open_fds
Created attachment 802131 [details] File: proc_pid_status
Created attachment 802132 [details] File: var_log_messages
Another user experienced a similar problem: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c 'const Main = imports.main; Main.start();' --no-default-window crash_function: object_instance_finalize executable: /usr/bin/gjs-console kernel: 3.12.5-302.fc20.x86_64 package: gjs-1.38.1-1.fc20 reason: gjs-console killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: The system doesn't "frozen", just appeared an error message. reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c 'const Main = imports.main; Main.start();' --no-default-window crash_function: object_instance_finalize executable: /usr/bin/gjs-console kernel: 3.12.7-300.fc20.x86_64 package: gjs-1.38.1-1.fc20 reason: gjs-console killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I altered the Java application priority at the system monitor to the very high priority. Nothing has happened (no crash), just an error message. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c 'const Main = imports.main; Main.start();' --no-default-window crash_function: object_instance_finalize executable: /usr/bin/gjs-console kernel: 3.13.3-201.fc20.x86_64 package: gjs-1.38.1-1.fc20 reason: gjs-console killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: re run compare operation in meld reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c 'const Main = imports.main; Main.start();' --no-default-window crash_function: object_instance_finalize executable: /usr/bin/gjs-console kernel: 3.13.6-200.fc20.x86_64 package: gjs-1.38.1-1.fc20 reason: gjs-console killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.