Version-Release number of selected component: firefox-61.0.1-3.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox -contentproc -childID 1 -isForBrowser -prefsLen 9610 -schedulerPrefs 0001,2 -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 10052 tab crash_function: mozilla::ipc::MessageChannel::OnChannelErrorFromLink() executable: /usr/lib64/firefox/firefox journald_cursor: s=2bc2a7f7a9c249e79d77a8ac7b6bf863;i=8b9;b=be047efc69a74eeb82f114bfc4e3ab3c;m=2cb9d442;t=572b52f74ad42;x=7c9bd27503744589 kernel: 4.17.12-200.amdgpu.fc28.ppc64le rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (10 frames) #0 mozilla::ipc::MessageChannel::OnChannelErrorFromLink() at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/glue/MessageChannel.cpp:2556 #1 mozilla::ipc::ProcessLink::OnChannelError() at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/glue/MessageLink.cpp:393 #2 IPC::Channel::ChannelImpl::OnFileCanReadWithoutBlocking(int) at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/chrome/common/ipc_channel_posix.cc:822 #3 base::MessagePumpLibevent::OnLibeventNotification(int, short, void*) at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/base/message_pump_libevent.cc:255 #4 event_persist_closure at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/third_party/libevent/event.c:1580 #5 event_process_active_single_queue at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/third_party/libevent/event.c:1639 #6 event_process_active at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/third_party/libevent/event.c:1738 #7 event_base_loop at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/third_party/libevent/event.c:1961 #8 base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/base/message_pump_libevent.cc:381 #9 MessageLoop::RunInternal() at /usr/src/debug/firefox-61.0.1-3.fc28.ppc64le/ipc/chromium/src/base/message_loop.cc:592
Created attachment 1473490 [details] File: backtrace
Created attachment 1473491 [details] File: cgroup
Created attachment 1473492 [details] File: core_backtrace
Created attachment 1473493 [details] File: cpuinfo
Created attachment 1473494 [details] File: dso_list
Created attachment 1473495 [details] File: environ
Created attachment 1473496 [details] File: limits
Created attachment 1473497 [details] File: maps
Created attachment 1473498 [details] File: mountinfo
Created attachment 1473499 [details] File: open_fds
Created attachment 1473500 [details] File: proc_pid_status
Similar problem has been detected: Typing in the Firefox address bar on ppc64le on a Talos reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox -contentproc -childID 1 -isForBrowser -prefsLen 5548 -schedulerPrefs 0001,2 -parentBuildID 20180904094357 -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 3454 tab crash_function: mozilla::ipc::MessageChannel::OnChannelErrorFromLink() executable: /usr/lib64/firefox/firefox journald_cursor: s=7de50377476c41018f0433caac4b36c1;i=3875;b=309021d3f9ad4bcc86613b4aef5fe17a;m=53b8700;t=57578384f1c3f;x=c1049d1430904ea9 kernel: 4.17.19-200.fc28.ppc64le package: firefox-62.0-2.fc28 reason: firefox killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Is anyone able to reproduce the crash with FF from the mozilla-central repo (top of the upstream repo)?
mozilla-central doesn't build due to issues related to: https://fedoraproject.org/wiki/Changes/PPC64LE_Float128_Transition
Not sure it's exactly related to the Float128 transition change, but I have reported the rust crash due float128 in bug 1633565.
firefox-63.0.1-5.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-e485c3c4cb
firefox-63.0.1-5.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.