Description of problem: Thunderbird just coredumps at startup. Version-Release number of selected component: thunderbird-60.0-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/thunderbird/thunderbird crash_function: WasmFaultHandler(int, siginfo_t*, void*) executable: /usr/lib64/thunderbird/thunderbird journald_cursor: s=97e70be1b46c479687ffbd1969c53a9e;i=4c74;b=a175817e7c8f46dd8e96680604ddcb3c;m=7543256c;t=575f0550d7660;x=b5476cb6ff912115 kernel: 4.18.5-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (1 frames) #2 WasmFaultHandler(int, siginfo_t*, void*) at /usr/src/debug/thunderbird-60.0-1.fc28.x86_64/js/src/wasm/WasmSignalHandlers.cpp:1501
Created attachment 1483581 [details] File: backtrace
Created attachment 1483582 [details] File: cgroup
Created attachment 1483583 [details] File: core_backtrace
Created attachment 1483584 [details] File: cpuinfo
Created attachment 1483585 [details] File: dso_list
Created attachment 1483586 [details] File: environ
Created attachment 1483587 [details] File: limits
Created attachment 1483588 [details] File: maps
Created attachment 1483589 [details] File: mountinfo
Created attachment 1483590 [details] File: open_fds
Created attachment 1483591 [details] File: proc_pid_status
Similar problem has been detected: Thunderbird was sitting idle. As far as I can tell after restarting, no messages arrived just before the crash. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/lib64/thunderbird/thunderbird crash_function: WasmFaultHandler(int, siginfo_t*, void*) executable: /usr/lib64/thunderbird/thunderbird journald_cursor: s=996e3814441b433889c53ae03c8aee4a;i=1a004c5;b=08f026e8ed9d493fb37132286481a2e8;m=48d7bff22d6;t=5763fb3d41e09;x=2c6f40266009d256 kernel: 4.17.7-200.fc28.x86_64 package: thunderbird-60.0-1.fc28 reason: thunderbird killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Crash circumstances in my case are similar to bug 1544467 and bug 1595281.
*** Bug 1636910 has been marked as a duplicate of this bug. ***
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.
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.