Bug 2260322

Summary: [abrt] seamonkey: nsProfileLock::FatalSignalHandler(): seamonkey killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Karel Volný <kvolny>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: dmitry, gecko-bugs-nobody, kvolny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6df5d38d94527a4c44fc36068125b9c82b2f11a
Whiteboard: abrt_hash:fd93a884902fa15be7bef8b531e5289f02bd6b54;VARIANT_ID=;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 22:46:27 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 Karel Volný 2024-01-25 10:18:19 UTC
Description of problem:
Don't know, I've just left it opened overnight and it crashed in the morning, before I've even touched it ...

Version-Release number of selected component:
seamonkey-2.53.18.1-1.fc39

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         seamonkey killed by SIGSEGV
journald_cursor: s=8569f58519a34d179d29250db33a8f6c;i=13b51e7f;b=854540fd4f2e4972aa3c6528be8e74b5;m=c89de767b1;t=60fc05ad02f7e;x=edbe3677f116a45
executable:     /usr/lib64/seamonkey/seamonkey
cmdline:        /usr/bin/seamonkey
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-seamonkey-f0083099e0604213a378e17c365656d4.scope
rootdir:        /
uid:            1000
kernel:         6.6.11-200.fc39.x86_64
package:        seamonkey-2.53.18.1-1.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: nsProfileLock::FatalSignalHandler
comment:        Don't know, I've just left it opened overnight and it crashed in the morning, before I've even touched it ...

Truncated backtrace:
Thread no. 0 (2 frames)
 #3 nsProfileLock::FatalSignalHandler at /usr/src/debug/seamonkey-2.53.18.1-1.fc39.x86_64/mozilla/toolkit/profile/nsProfileLock.cpp:177
 #4 WasmFaultHandler at /usr/src/debug/seamonkey-2.53.18.1-1.fc39.x86_64/mozilla/js/src/wasm/WasmSignalHandlers.cpp:1459

Comment 1 Karel Volný 2024-01-25 10:18:23 UTC
Created attachment 2010448 [details]
File: proc_pid_status

Comment 2 Karel Volný 2024-01-25 10:18:25 UTC
Created attachment 2010449 [details]
File: maps

Comment 3 Karel Volný 2024-01-25 10:18:26 UTC
Created attachment 2010450 [details]
File: limits

Comment 4 Karel Volný 2024-01-25 10:18:28 UTC
Created attachment 2010451 [details]
File: environ

Comment 5 Karel Volný 2024-01-25 10:18:30 UTC
Created attachment 2010452 [details]
File: open_fds

Comment 6 Karel Volný 2024-01-25 10:18:32 UTC
Created attachment 2010453 [details]
File: mountinfo

Comment 7 Karel Volný 2024-01-25 10:18:34 UTC
Created attachment 2010454 [details]
File: os_info

Comment 8 Karel Volný 2024-01-25 10:18:35 UTC
Created attachment 2010455 [details]
File: cpuinfo

Comment 9 Karel Volný 2024-01-25 10:18:37 UTC
Created attachment 2010456 [details]
File: core_backtrace

Comment 10 Karel Volný 2024-01-25 10:18:39 UTC
Created attachment 2010457 [details]
File: var_log_messages

Comment 11 Karel Volný 2024-01-25 10:18:42 UTC
Created attachment 2010458 [details]
File: backtrace

Comment 12 JC 2024-05-03 21:32:27 UTC
Crashed when not being actively used. 


reporter:       libreport-2.17.11
type:           CCpp
reason:         seamonkey killed by SIGSEGV
journald_cursor: s=a58d77bfd69e4f74a061f819efdc82f4;i=2494c5;b=dda622051a344d48b5a744e260769b55;m=470bfff74c;t=6178a39c85cdd;x=3ac116bb974463b1
executable:     /usr/lib64/seamonkey/seamonkey
cmdline:        seamonkey -mail
cgroup:         0::/user.slice/user-1000.slice/session-4.scope
rootdir:        /
uid:            1000
kernel:         6.8.7-200.fc39.x86_64
package:        seamonkey-2.53.18.2-1.fc39
runlevel:       N 5
backtrace_rating: 4
crash_function: nsProfileLock::FatalSignalHandler
comment:        Crashed when not being actively used.

Comment 13 Aoife Moloney 2024-11-13 11:54:16 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 22:46:27 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.