Hide Forgot
Version-Release number of selected component: gjs-1.38.1-1.fc20 Additional info: reporter: libreport-2.1.9 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: dlmmap_locked executable: /usr/bin/gjs-console kernel: 3.12.0-2.fc21.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 dlmmap_locked at ../src/closures.c:460 #1 dlmmap at ../src/closures.c:506 #2 sys_alloc at ../src/dlmalloc.c:3515 #3 dlmalloc at ../src/dlmalloc.c:4245 #4 ffi_closure_alloc at ../src/closures.c:572 #5 g_callable_info_prepare_closure at girepository/girffi.c:365 #6 gjs_callback_trampoline_new at gi/function.c:476 #7 gjs_hook_up_vfunc at gi/object.c:2281 #8 CallJSNative at /usr/src/debug/mozjs17.0.0/js/src/jscntxtinlines.h:372 #9 js::InvokeKernel at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:352 Potential duplicate: bug 851966
Created attachment 830019 [details] File: backtrace
Created attachment 830020 [details] File: cgroup
Created attachment 830021 [details] File: core_backtrace
Created attachment 830022 [details] File: dso_list
Created attachment 830023 [details] File: environ
Created attachment 830024 [details] File: exploitable
Created attachment 830025 [details] File: limits
Created attachment 830026 [details] File: maps
Created attachment 830027 [details] File: open_fds
Created attachment 830029 [details] File: proc_pid_status
Created attachment 830031 [details] File: var_log_messages
Another user experienced a similar problem: It looks like stopped when I was rederizing my qt-recordMyDesktop video record. The weather application wasn't open in another window, probably was working in background. (tons of lag) reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/gjs /usr/share/org.gnome.Weather.Application/org.gnome.Weather.Application crash_function: dlmmap_locked executable: /usr/bin/gjs-console kernel: 3.13.8-200.fc20.x86_64 package: gjs-1.38.1-1.fc20 reason: gjs-console killed by SIGBUS 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.