Hide Forgot
Description of problem: Entering data into guardian.co.uk on icecat Version-Release number of selected component: icecat-38.8.0-5.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/lib64/icecat-38.8.0/plugin-container -greomni /usr/lib64/icecat-38.8.0/omni.ja -appomni /usr/lib64/icecat-38.8.0/browser/omni.ja -appdir /usr/lib64/icecat-38.8.0/browser 21226 tab crash_function: mozilla::layers::PCompositorChild::DeallocSubtree executable: /usr/lib64/icecat-38.8.0/plugin-container global_pid: 21359 kernel: 4.6.7-200.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 mozilla::layers::PCompositorChild::DeallocSubtree at /usr/src/debug/icecat-38.8.0/icecat-objdir/ipc/ipdl/PCompositorChild.cpp:1203 #1 mozilla::layers::PCompositorChild::OnChannelError at /usr/src/debug/icecat-38.8.0/icecat-objdir/ipc/ipdl/PCompositorChild.cpp:1098 #2 mozilla::ipc::MessageChannel::NotifyMaybeChannelError at /usr/src/debug/icecat-38.8.0/ipc/glue/MessageChannel.cpp:1609 #3 mozilla::ipc::MessageChannel::OnNotifyMaybeChannelError at /usr/src/debug/icecat-38.8.0/ipc/glue/MessageChannel.cpp:1638 #4 MessageLoop::DeferOrRunPendingTask at /usr/src/debug/icecat-38.8.0/ipc/chromium/src/base/message_loop.cc:361 #5 MessageLoop::DoWork at /usr/src/debug/icecat-38.8.0/ipc/chromium/src/base/message_loop.cc:447 #6 mozilla::ipc::DoWorkRunnable::Run at /usr/src/debug/icecat-38.8.0/ipc/glue/MessagePump.cpp:233 #7 nsThread::ProcessNextEvent at /usr/src/debug/icecat-38.8.0/xpcom/threads/nsThread.cpp:855 #8 NS_ProcessNextEvent at /usr/src/debug/icecat-38.8.0/xpcom/glue/nsThreadUtils.cpp:265 #9 mozilla::ipc::MessagePump::Run at /usr/src/debug/icecat-38.8.0/ipc/glue/MessagePump.cpp:99
Created attachment 1197424 [details] File: backtrace
Created attachment 1197425 [details] File: cgroup
Created attachment 1197426 [details] File: core_backtrace
Created attachment 1197427 [details] File: dso_list
Created attachment 1197428 [details] File: environ
Created attachment 1197429 [details] File: exploitable
Created attachment 1197430 [details] File: limits
Created attachment 1197431 [details] File: maps
Created attachment 1197432 [details] File: mountinfo
Created attachment 1197433 [details] File: namespaces
Created attachment 1197434 [details] File: open_fds
Created attachment 1197435 [details] File: proc_pid_status
Created attachment 1197436 [details] File: var_log_messages
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.