Description of problem: Since upgrading SeaMonkey from 2.53.21 to 2.53.22 it reproducibly crashes with SIGILL on exit. This didn't happen with 2.53.21 and it still happens after upgrading Fedora from 42 to 43 (MATE-Compiz). Version-Release number of selected component (if applicable): seamonkey-2.53.22-1.fc43.x86_64 How reproducible: Steps to Reproduce: 1. Execute command: seamonkey --safe-mode https://bodhi.fedoraproject.org/ & 2. Click "Continue in Safe Mode" 3. Wait until website is loaded. 4. Exit SeaMonkey (Ctrl-Q). Actual results: After a few seconds a notification appears: "We're sorry, it looks like a problem occurred". Applications -> System Tools -> Problem Reporting -> Details says: reason: seamonkey killed by SIGILL crash_function: WasmFaultHandler(int, siginfo_t, void) Expected results: No crash. Additional info:
Could you please also test how the "generic Linux version" (from my copr build) behaves in the same environment? This will help determine whether the problem is with the code itself or if it is a build environment issue (the "generic" version is built under epel8, and have some libraries bundled). Get it here: https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-8-x86_64/09770992-seamonkey/seamonkey-2.53.22-1.el8.x86_64.rpm
Well, upstream can reproduce it as well, but cannot resolve right now due to lack of time. In a hope you have enough time -- could you bisect the issue using the official nightly builds from https://archive.seamonkey-project.org/nightly/2025/index.html ? (Sorry if this is too ambitious a request. :) )
Sorry, I have absolutely no clue what to do with a "nightly build".
I've found that to reproduce the crash you need to trigger the Anubis bot check which https://bodhi.fedoraproject.org/ uses. For me the easiest way to do that is by creating a new profile each time you test With checking nightlies, the one from 2025-08-18 works, the one from 2025-08-19 crashes.
FEDORA-2026-f54e4ee85a (seamonkey-2.53.23-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f54e4ee85a
FEDORA-2026-f54e4ee85a has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f54e4ee85a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f54e4ee85a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
seamonkey-2.53.23-1.fc43 fixes the problem for me. Thanks!
FEDORA-2026-f54e4ee85a (seamonkey-2.53.23-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 2428564 has been marked as a duplicate of this bug. ***