Thunderbird crashes after providing primary password during startup due to failed memory allocation, or hangs - "failed to allocate new chunk during GC"
Categories
(Thunderbird :: General, defect)
Tracking
(thunderbird_esr91 affected, thunderbird99 unaffected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr91 | --- | affected |
| thunderbird99 | --- | unaffected |
People
(Reporter: zjosua, Unassigned)
Details
(4 keywords)
User Agent: Mozilla/5.0 (X11; Linux i686; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
- start thunderbird from qterminal or lxqt-runner
- enter primary password
- wait
Actual results:
After a few seconds, thunderbird either closes again or freezes until I forcibly close it by sending SIGKILL with htop or Ctrl+C when launched from qterminal.
The terminal shows (These are from two separate attempts at starting thunderbird. The second output occurs way more often than the first one.):
zjosua@debian:~$ thunderbird
Hit MOZ_CRASH([unhandlable oom] Failed to allocate new chunk during GC) at ./js/src/vm/JSContext.cpp:1213
ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal...
11699
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
zjosua@debian:~$ thunderbird
memory allocation of 262144 bytes failed
Redirecting call to abort() to mozalloc_abort
ExceptionHandler::GenerateDump cloned child 11910
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
^CExiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Expected results:
Thunderbird starts normally (duh).
It's working better in troubleshoot mode (thunderbird doesn't crash right after starting, before I could do anything), but I still had two crashes so far:
This one was while thunderbird was just open in the background:
zjosua@debian:~$ thunderbird --safe-mode
[GFX1-]: Failed buffer for 212, 55, 1228, 820
[GFX1-]: Failed buffer for 212, 55, 1228, 820
[GFX1-]: Failed buffer for 0, 0, 970, 1482
[GFX1-]: Failed buffer for 0, 0, 1428, 2944
[GFX1-]: Failed buffer for 0, 0, 1428, 2944
(thunderbird:8655): GLib-GObject-WARNING **: 07:40:49.118: ../../../gobject/gsignal.c:3599: signal name 'selection_changed' is invalid for instance '0x1b6c78' of type 'MaiAtkType3'
(thunderbird:8655): GLib-GObject-WARNING **: 07:40:55.074: ../../../gobject/gsignal.c:3599: signal name 'selection_changed' is invalid for instance '0x1a06d8' of type 'MaiAtkType3'
(thunderbird:8655): GLib-GObject-WARNING **: 07:40:58.915: ../../../gobject/gsignal.c:3599: signal name 'selection_changed' is invalid for instance '0x1b6c78' of type 'MaiAtkType3'
Hit MOZ_CRASH([unhandlable oom] Failed to allocate new chunk during GC) at ./js/src/vm/JSContext.cpp:1213
ExceptionHandler::GenerateDump cloned child 10359ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
And here when I tried to save an attachment:
zjosua@debian:~$ thunderbird --safe-mode
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)
(thunderbird:10815): GLib-ERROR **: 09:00:10.993: creating thread '[pango] FcFontSetMatch': Error creating thread: Resource temporarily unavailable
ExceptionHandler::GenerateDump cloned child 11081
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Trace/breakpoint trap
I was however able to save the same attachment in the second attempt.
|
||
Comment 3•4 years ago
|
||
How long have you been running version 91?
Are you using Thunderbird downloaded from https://www.thunderbird.net/en-US/ ?
I am using thunderbird from the debian testing repo. I don't remember when exactly I updated to version 91, but it's in the repo since Nov 29th 2021.
I had briefly tried using the thunderbird binary downloaded from thunderbird.net when the problems started, but the behaviour was unchanged.
|
|
||
Comment 5•4 years ago
|
||
I have no idea. It's stretch, but you might try beta shwn at the bottom of https://www.thunderbird.net/en-US/
(In reply to Wayne Mery (:wsmwk) from comment #5)
I have no idea. It's stretch, but you might try beta shwn at the bottom of https://www.thunderbird.net/en-US/
Thanks for the suggestion.
The beta works great so far, even without using the troubleshoot mode.
Yes, so far I didn't see any crashes with the beta.
|
|
||
Comment 9•4 years ago
|
||
Thanks for the info. Perhaps one of these, but hard to say https://mzl.la/3iIWfOc
|
|
||
Comment 10•4 years ago
|
||
Frustrating when we can't identify the exact cause. Similar (for version 91) is Bug 1759723 - Thunderbird crashes as soon as it starts syncing with my Fastmail account (startup), and in troubleshoot mode (Windows user)
I have startup crashes primarily on beta Bug 1743138 - Startup crash in [@ nsMsgAttachmentData::~nsMsgAttachmentData]
|
|
||
Comment 11•3 years ago
|
||
WFM per reporter
Description
•