Bug 2428564 - [abrt] seamonkey: nsProfileLock::FatalSignalHandler(): seamonkey killed by SIGILL
Summary: [abrt] seamonkey: nsProfileLock::FatalSignalHandler(): seamonkey killed by SI...
Keywords:
Status: CLOSED DUPLICATE of bug 2415167
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 42
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Horak
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:fd93a884902fa15be7bef8b531e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-11 16:04 UTC by JC
Modified: 2026-01-11 22:00 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-01-11 22:00:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.49 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: maps (3.99 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: limits (1.29 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: environ (6.34 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: open_fds (4.66 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: mountinfo (3.63 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: os_info (726 bytes, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: cpuinfo (3.54 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: core_backtrace (57.65 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: dso_list (341 bytes, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details
File: backtrace (249.43 KB, text/plain)
2026-01-11 16:05 UTC, JC
no flags Details

Description JC 2026-01-11 16:04:57 UTC
Description of problem:


Version-Release number of selected component:
seamonkey-2.53.22-1.fc42

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         seamonkey killed by SIGILL
journald_cursor: s=571c785a527648c08fa6a1bc82c5e937;i=312a45b;b=4ce709572d3b45b3b1d0129f85c44eff;m=5dba4187b4;t=6481ea763a7d9;x=3206d4252ca02dc9
executable:     /usr/lib64/seamonkey/seamonkey
cmdline:        seamonkey -mail
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
rootdir:        /
uid:            1000
kernel:         6.17.13-200.fc42.x86_64
package:        seamonkey-2.53.22-1.fc42
runlevel:       N 5
backtrace_rating: 4
crash_function: nsProfileLock::FatalSignalHandler
comment:        

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


Potential duplicate: bug 2260322

Comment 1 JC 2026-01-11 16:05:01 UTC
Created attachment 2121804 [details]
File: proc_pid_status

Comment 2 JC 2026-01-11 16:05:03 UTC
Created attachment 2121805 [details]
File: maps

Comment 3 JC 2026-01-11 16:05:05 UTC
Created attachment 2121806 [details]
File: limits

Comment 4 JC 2026-01-11 16:05:06 UTC
Created attachment 2121807 [details]
File: environ

Comment 5 JC 2026-01-11 16:05:08 UTC
Created attachment 2121808 [details]
File: open_fds

Comment 6 JC 2026-01-11 16:05:10 UTC
Created attachment 2121809 [details]
File: mountinfo

Comment 7 JC 2026-01-11 16:05:11 UTC
Created attachment 2121810 [details]
File: os_info

Comment 8 JC 2026-01-11 16:05:13 UTC
Created attachment 2121811 [details]
File: cpuinfo

Comment 9 JC 2026-01-11 16:05:15 UTC
Created attachment 2121812 [details]
File: core_backtrace

Comment 10 JC 2026-01-11 16:05:17 UTC
Created attachment 2121813 [details]
File: dso_list

Comment 11 JC 2026-01-11 16:05:19 UTC
Created attachment 2121814 [details]
File: backtrace

Comment 12 JC 2026-01-11 16:10:33 UTC
I'd had seamonkey running and activated protonvpn client. Then I closed seamonkey and the crash occurred.

Comment 13 Dmitry Butskoy 2026-01-11 22:00:56 UTC

*** This bug has been marked as a duplicate of bug 2415167 ***


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