Bug 1623231 - [abrt] firefox: mozilla::EnterChroot(): firefox killed by SIGSEGV
Summary: [abrt] firefox: mozilla::EnterChroot(): firefox killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7781b12a453af16b16b3bfeb3a0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-28 19:38 UTC by sedrubal
Modified: 2019-05-28 23:08 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:08:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (58.36 KB, text/plain)
2018-08-28 19:38 UTC, sedrubal
no flags Details
File: cgroup (331 bytes, text/plain)
2018-08-28 19:38 UTC, sedrubal
no flags Details
File: core_backtrace (57.02 KB, text/plain)
2018-08-28 19:38 UTC, sedrubal
no flags Details
File: cpuinfo (1.41 KB, text/plain)
2018-08-28 19:38 UTC, sedrubal
no flags Details
File: dso_list (9.67 KB, text/plain)
2018-08-28 19:38 UTC, sedrubal
no flags Details
File: environ (3.20 KB, text/plain)
2018-08-28 19:38 UTC, sedrubal
no flags Details
File: exploitable (82 bytes, text/plain)
2018-08-28 19:39 UTC, sedrubal
no flags Details
File: limits (1.29 KB, text/plain)
2018-08-28 19:39 UTC, sedrubal
no flags Details
File: maps (61.49 KB, text/plain)
2018-08-28 19:39 UTC, sedrubal
no flags Details
File: mountinfo (3.77 KB, text/plain)
2018-08-28 19:39 UTC, sedrubal
no flags Details
File: open_fds (2.34 KB, text/plain)
2018-08-28 19:39 UTC, sedrubal
no flags Details
File: proc_pid_status (1.32 KB, text/plain)
2018-08-28 19:39 UTC, sedrubal
no flags Details

Description sedrubal 2018-08-28 19:38:46 UTC
Version-Release number of selected component:
firefox-61.0.2-3.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/lib64/firefox/firefox -contentproc -childID 4 -isForBrowser -prefsLen 35341 -schedulerPrefs 0001,2 -greomni /usr/lib64/firefox/omni.ja -appomni /usr/lib64/firefox/browser/omni.ja -appdir /usr/lib64/firefox/browser 4298 true tab
crash_function: mozilla::EnterChroot
executable:     /usr/lib64/firefox/firefox
journald_cursor: s=db0516c4b79c4d5b9f982eb26dcb6ddd;i=6e8a;b=826ec117af8b4693b7421d275004f4fa;m=f656d2f;t=57482b0a7a7b0;x=4be15f5082b0a4fb
kernel:         4.17.18-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 0 (10 frames)
 #0 mozilla::EnterChroot at /usr/src/debug/firefox-61.0.2-3.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-61.0.2-3.fc28.x86_64/security/sandbox/linux/Sandbox.cpp:599
 #2 mozilla::SetContentProcessSandbox(mozilla::ContentProcessSandboxParams&&) at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/security/sandbox/linux/Sandbox.cpp:633
 #3 mozilla::dom::ContentChild::RecvSetProcessSandbox(mozilla::dom::MaybeFileDesc const&) at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/dom/ipc/ContentChild.cpp:1733
 #4 mozilla::dom::PContentChild::OnMessageReceived(IPC::Message const&) at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/objdir/ipc/ipdl/PContentChild.cpp:5882
 #5 mozilla::ipc::MessageChannel::DispatchAsyncMessage(IPC::Message const&) at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/ipc/glue/MessageChannel.cpp:2142
 #6 mozilla::ipc::MessageChannel::DispatchMessage(IPC::Message&&) at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/ipc/glue/MessageChannel.cpp:2072
 #7 mozilla::ipc::MessageChannel::RunMessage(mozilla::ipc::MessageChannel::MessageTask&) at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/ipc/glue/MessageChannel.cpp:1918
 #8 mozilla::ipc::MessageChannel::MessageTask::Run() at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/ipc/glue/MessageChannel.cpp:1951
 #9 nsThread::ProcessNextEvent(bool, bool*) at /usr/src/debug/firefox-61.0.2-3.fc28.x86_64/xpcom/threads/nsThread.cpp:1090

Comment 1 sedrubal 2018-08-28 19:38:52 UTC
Created attachment 1479346 [details]
File: backtrace

Comment 2 sedrubal 2018-08-28 19:38:53 UTC
Created attachment 1479347 [details]
File: cgroup

Comment 3 sedrubal 2018-08-28 19:38:55 UTC
Created attachment 1479348 [details]
File: core_backtrace

Comment 4 sedrubal 2018-08-28 19:38:56 UTC
Created attachment 1479349 [details]
File: cpuinfo

Comment 5 sedrubal 2018-08-28 19:38:58 UTC
Created attachment 1479350 [details]
File: dso_list

Comment 6 sedrubal 2018-08-28 19:38:59 UTC
Created attachment 1479351 [details]
File: environ

Comment 7 sedrubal 2018-08-28 19:39:00 UTC
Created attachment 1479352 [details]
File: exploitable

Comment 8 sedrubal 2018-08-28 19:39:02 UTC
Created attachment 1479353 [details]
File: limits

Comment 9 sedrubal 2018-08-28 19:39:03 UTC
Created attachment 1479354 [details]
File: maps

Comment 10 sedrubal 2018-08-28 19:39:05 UTC
Created attachment 1479355 [details]
File: mountinfo

Comment 11 sedrubal 2018-08-28 19:39:06 UTC
Created attachment 1479356 [details]
File: open_fds

Comment 12 sedrubal 2018-08-28 19:39:07 UTC
Created attachment 1479357 [details]
File: proc_pid_status

Comment 13 Ben Cotton 2019-05-02 19:22:32 UTC
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.

Comment 14 Ben Cotton 2019-05-02 20:26:10 UTC
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.

Comment 15 Ben Cotton 2019-05-28 23:08:52 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.