Bug 2196913

Summary: [abrt] firefox: nsProfileLock::FatalSignalHandler(): firefox killed by SIGSEGV
Product: [Fedora] Fedora Reporter: anas <anas.blinux>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: anas.blinux, erack, gecko-bugs-nobody, jhorak, klaas, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/78016422a8880e654b0bd4713cca5ee2c4b3a15
Whiteboard: abrt_hash:77e44cb5d9479182bc7b7736d58c681555a9efab;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 21:11:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: var_log_messages
none
File: backtrace none

Description anas 2023-05-10 18:52:10 UTC
Description of problem:
crash when browsing websites

Version-Release number of selected component:
firefox-112.0.2-1.fc39

Additional info:
reporter:       libreport-2.17.9
type:           CCpp
reason:         firefox killed by SIGSEGV
journald_cursor: s=73b50dc1c3fa42e0bd26938cf31cc955;i=1158;b=63450ee0279d49ad9d1f334d5b43e838;m=100f8af31;t=5fb5af71ac067;x=b5f53eac3ed068d9
executable:     /usr/lib64/firefox/firefox
cmdline:        /usr/lib64/firefox/firefox
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-firefox-20170.scope/20170
rootdir:        /
uid:            1000
kernel:         6.4.0-0.rc1.20230509gitba0ad6ed89fd.17.fc39.x86_64
package:        firefox-112.0.2-1.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: nsProfileLock::FatalSignalHandler
comment:        crash when browsing websites

Truncated backtrace:
Thread no. 0 (22 frames)
 #3 nsProfileLock::FatalSignalHandler at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/toolkit/profile/nsProfileLock.cpp:174
 #5 NS_ABORT_OOM at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/xpcom/base/nsDebugImpl.cpp:674
 #6 nsTArrayInfallibleAllocator::SizeTooBig at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/objdir/dist/include/nsTArray.h:263
 #7 nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_RelocateUsingMemutils>::EnsureCapacity<nsTArrayInfallibleAllocator> at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/objdir/dist/include/nsTArray-inl.h:167
 #8 nsTArray_Impl<mozilla::OldItemInfo, nsTArrayInfallibleAllocator>::AppendElementInternal<nsTArrayInfallibleAllocator, mozilla::OldItemInfo> at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/objdir/dist/include/nsTArray.h:2669
 #9 nsTArray<mozilla::OldItemInfo>::AppendElement<mozilla::OldItemInfo> at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/objdir/dist/include/nsTArray.h:2810
 #10 mozilla::RetainedDisplayListBuilder::PreProcessDisplayList at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/painting/RetainedDisplayListBuilder.cpp:240
 #13 mozilla::RetainedDisplayListBuilder::AttemptPartialUpdate at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/painting/nsDisplayList.h:425
 #14 nsLayoutUtils::PaintFrame at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsLayoutUtils.cpp:3323
 #15 mozilla::PresShell::PaintInternal at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/objdir/dist/include/mozilla/gfx/RectAbsolute.h:43
 #16 mozilla::PresShell::PaintAndRequestComposite at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/PresShell.cpp:6302
 #17 nsViewManager::ProcessPendingUpdatesPaint at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/view/nsViewManager.cpp:433
 #18 nsViewManager::ProcessPendingUpdatesForView at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/view/nsViewManager.cpp:368
 #19 nsViewManager::ProcessPendingUpdates at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/view/nsViewManager.cpp:941
 #21 nsRefreshDriver::Tick at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:2824
 #22 mozilla::RefreshDriverTimer::TickDriver at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:373
 #23 mozilla::RefreshDriverTimer::TickRefreshDrivers at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:351
 #24 mozilla::RefreshDriverTimer::Tick at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:367
 #25 mozilla::VsyncRefreshDriverTimer::RunRefreshDrivers at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:911
 #26 mozilla::VsyncRefreshDriverTimer::TickRefreshDriver at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:825
 #27 mozilla::VsyncRefreshDriverTimer::NotifyVsyncOnMainThread at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:746
 #28 mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsyncTimerOnMainThread at /usr/src/debug/firefox-112.0.2-1.fc39.x86_64/layout/base/nsRefreshDriver.cpp:592

Comment 1 anas 2023-05-10 18:52:13 UTC
Created attachment 1963831 [details]
File: proc_pid_status

Comment 2 anas 2023-05-10 18:52:15 UTC
Created attachment 1963832 [details]
File: maps

Comment 3 anas 2023-05-10 18:52:16 UTC
Created attachment 1963833 [details]
File: limits

Comment 4 anas 2023-05-10 18:52:18 UTC
Created attachment 1963834 [details]
File: environ

Comment 5 anas 2023-05-10 18:52:20 UTC
Created attachment 1963835 [details]
File: open_fds

Comment 6 anas 2023-05-10 18:52:21 UTC
Created attachment 1963836 [details]
File: mountinfo

Comment 7 anas 2023-05-10 18:52:23 UTC
Created attachment 1963837 [details]
File: os_info

Comment 8 anas 2023-05-10 18:52:25 UTC
Created attachment 1963838 [details]
File: cpuinfo

Comment 9 anas 2023-05-10 18:52:27 UTC
Created attachment 1963839 [details]
File: core_backtrace

Comment 10 anas 2023-05-10 18:52:29 UTC
Created attachment 1963840 [details]
File: var_log_messages

Comment 11 anas 2023-05-10 18:52:31 UTC
Created attachment 1963841 [details]
File: backtrace

Comment 12 Fedora Release Engineering 2023-08-16 07:14:09 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 13 Aoife Moloney 2024-11-08 10:52:17 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
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
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 14 Aoife Moloney 2024-11-27 21:11:51 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.