Description of problem: Unknown as to how it occurred. Launched Firefox, then the notification appeared that FIrefox crashed, yet it did not appear to restarrt. Version-Release number of selected component: firefox-60.0.1-6.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox -contentproc -childID 2 -isForBrowser -boolPrefs 36:1|183:1|259:1|299:0|309:0| -stringPrefs 285:36;c7fe1b8f-8af9-4a4b-9df8-5a86a22eef32| -schedulerPrefs 0001,2 -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 3045 true tab crash_function: mozilla::EnterChroot executable: /usr/lib64/firefox/firefox journald_cursor: s=4c15eab3a57a4ca4b5cc4c749bade99f;i=2d059;b=58e7abc8c7564dce82ba938b10840807;m=286d6a55;t=56e40cb83de50;x=76975a43c72d59f1 kernel: 4.16.14-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 mozilla::EnterChroot at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/security/sandbox/linux/Sandbox.cpp:310 #1 mozilla::SetCurrentProcessSandbox(mozilla::UniquePtr<sandbox::bpf_dsl::Policy, mozilla::DefaultDelete<sandbox::bpf_dsl::Policy> >) at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/security/sandbox/linux/Sandbox.cpp:599 #2 mozilla::SetContentProcessSandbox at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/security/sandbox/linux/Sandbox.cpp:633 #3 mozilla::dom::ContentChild::RecvSetProcessSandbox at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/dom/ipc/ContentChild.cpp:1715 #4 mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/objdir/ipc/ipdl/PContentChild.cpp:5639 #5 mozilla::ipc::MessageChannel::DispatchAsyncMessage(IPC::Message const&) at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/ipc/glue/MessageChannel.cpp:2133 #6 mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/ipc/glue/MessageChannel.cpp:2063 #7 mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/ipc/glue/MessageChannel.cpp:1909 #8 mozilla::ipc::MessageChannel::MessageTask::Run() at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/ipc/glue/MessageChannel.cpp:1942 #9 nsThread::ProcessNextEvent(bool, bool*) at /usr/src/debug/firefox-60.0.1-6.fc28.x86_64/xpcom/threads/nsThread.cpp:1040
Created attachment 1449541 [details] File: backtrace
Created attachment 1449542 [details] File: cgroup
Created attachment 1449543 [details] File: core_backtrace
Created attachment 1449544 [details] File: cpuinfo
Created attachment 1449545 [details] File: dso_list
Created attachment 1449546 [details] File: environ
Created attachment 1449547 [details] File: exploitable
Created attachment 1449548 [details] File: limits
Created attachment 1449549 [details] File: maps
Created attachment 1449550 [details] File: mountinfo
Created attachment 1449551 [details] File: open_fds
Created attachment 1449552 [details] File: proc_pid_status
*** Bug 1591695 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just web browsing and had a YouTube live stream playing, then the crash reported, but Firefox did not close. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox -contentproc -childID 7 -isForBrowser -prefsLen 20501 -schedulerPrefs 0001,2 -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 1851 true tab crash_function: mozilla::EnterChroot executable: /usr/lib64/firefox/firefox journald_cursor: s=4c15eab3a57a4ca4b5cc4c749bade99f;i=3fbc6;b=20638913a1ae473ebfa6f2cd60a9b862;m=61e31d8a;t=56ff3939ed043;x=e7c017b7953d584a kernel: 4.17.2-200.fc28.x86_64 package: firefox-61.0-4.fc28 reason: firefox killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1598375 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Firefox launched after the crash reporter submitted a crash report, and the crash reporter launched for a Firefox crash although Firefox did not close as a result of the crash. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox -contentproc -childID 2 -isForBrowser -prefsLen 16768 -schedulerPrefs 0001,2 -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 4821 true tab crash_function: mozilla::EnterChroot executable: /usr/lib64/firefox/firefox journald_cursor: s=4c15eab3a57a4ca4b5cc4c749bade99f;i=4e1e4;b=c8261c6cc2994ee6a13f6434251ea8d9;m=1195a5886;t=570c3aba1c968;x=33edfdad08c8f0b6 kernel: 4.17.3-200.fc28.x86_64 package: firefox-61.0-4.fc28 reason: firefox killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1603108 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Opened the link in a new tab. https://www.opennet.ru/opennews/art.shtml?num=49085 → https://en.wikipedia.org/wiki/Star_Ruler reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox -contentproc -childID 16 -isForBrowser -prefsLen 14568 -schedulerPrefs 0001,2 -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 2241 true tab crash_function: mozilla::EnterChroot executable: /usr/lib64/firefox/firefox journald_cursor: s=d7b8957c8cb94d40adb6987cbdb79311;i=4e406;b=a2bff9e1ab79429794e894bdf376df20;m=b6027193;t=572c1bc8608e7;x=5cd65b2f4805f146 kernel: 4.17.11-200.fc28.x86_64 package: firefox-61.0.1-3.fc28 reason: firefox killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.