Hide Forgot
Description of problem: I searched in bugzilla.redhat.com and clicked on result (https://bugzilla.redhat.com/show_bug.cgi?id=1215792) and after the page loaded firefox crashed. Version-Release number of selected component: firefox-50.0-1.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib64/firefox/firefox global_pid: 28581 kernel: 4.8.8-200.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 nsProfileLock::FatalSignalHandler at /usr/src/debug/firefox-50.0/firefox-50.0/toolkit/profile/nsProfileLock.cpp:181 #2 AsmJSFaultHandler<(Signal)0> at /usr/src/debug/firefox-50.0/firefox-50.0/js/src/asmjs/WasmSignalHandlers.cpp:1204 #5 Abort at /usr/src/debug/firefox-50.0/firefox-50.0/xpcom/base/nsDebugImpl.cpp:449 #6 NS_DebugBreak at /usr/src/debug/firefox-50.0/firefox-50.0/xpcom/base/nsDebugImpl.cpp:436 #7 X11Error at /usr/src/debug/firefox-50.0/firefox-50.0/toolkit/xre/nsX11ErrorHandler.cpp:147 #8 GdkErrorHandler at /usr/src/debug/firefox-50.0/firefox-50.0/toolkit/xre/nsGDKErrorHandler.cpp:83 #17 XTranslateCoordinates at TrCoords.c:51 #18 gdk_window_x11_get_root_coords at gdkwindow-x11.c:3123 #19 gdk_window_get_origin at gdkwindow.c:6451 #20 nsWindow::WidgetToScreenOffset at /usr/src/debug/firefox-50.0/firefox-50.0/widget/gtk/nsWindow.cpp:1882 Potential duplicate: bug 1397214
Created attachment 1223895 [details] File: backtrace
Created attachment 1223896 [details] File: cgroup
Created attachment 1223897 [details] File: core_backtrace
Created attachment 1223898 [details] File: dso_list
Created attachment 1223899 [details] File: environ
Created attachment 1223900 [details] File: limits
Created attachment 1223901 [details] File: maps
Created attachment 1223902 [details] File: mountinfo
Created attachment 1223903 [details] File: namespaces
Created attachment 1223904 [details] File: open_fds
Created attachment 1223905 [details] File: proc_pid_status
Created attachment 1223906 [details] File: var_log_messages
*** Bug 1398916 has been marked as a duplicate of this bug. ***
*** Bug 1402506 has been marked as a duplicate of this bug. ***
Happens for me too.
*** Bug 1405379 has been marked as a duplicate of this bug. ***
*** Bug 1411820 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.