1524247 - Thunderbird Shutdown crash/hang due to endless wait loop when no password is entered | WaitForSingleObjectEx | WaitForSingleObject | _PR_MD_WAIT_CV | _PR_WaitCondVar | PR_WaitCondVar | mozilla::CondVar::Wait | nsEventQueue::GetEvent

Status: NEW

(MailNews Core :: Networking: IMAP, defect)

Description

[Wayne Mery (:wsmwk)]

+++ This bug was initially created as a clone of Bug #1257058 +++

Unclear what impact the patch in Bug 1257058 had. But three signatures still topcrashes. With very similar, and somewhat odd history graphs. Note, the increase in crash volume over time can I think be attributed to users updating to version 60

#1 https://crash-stats.mozilla.com/signature/?release_channel=release&signature=shutdownhang%20%7C%20arena_t%3A%3AGetNonFullBinRun%20%7C%20nsThread%3A%3AShutdown%20%7C%20nsThreadManager%3A%3AShutdown&date=%3E%3D2018-07-31T04%3A33%3A29.000Z&date=%3C2019-01-31T02%3A33%3A29.000Z#graphs

#3 https://crash-stats.mozilla.com/signature/?release_channel=release&signature=shutdownhang%20%7C%20mozilla%3A%3AQueue%3CT%3E%3A%3APush&date=%3E%3D2018-07-31T04%3A32%3A56.000Z&date=%3C2019-01-31T02%3A32%3A56.000Z#graphs

#12 https://crash-stats.mozilla.com/signature/?release_channel=release&signature=shutdownhang%20%7C%20nsCOMPtr_base%3A%3Aassign_with_AddRef%20%7C%20mozilla%3A%3Adetail%3A%3AMutexImpl%3A%3Aunlock%20%7C%20nsThread%3A%3AShutdown%20%7C%20nsThreadManager%3A%3AShutdown&date=%3E%3D2018-07-31T04%3A33%3A55.000Z&date=%3C2019-01-31T02%3A33%3A55.000Z#graphs

and maybe this one
#70 https://crash-stats.mozilla.com/signature/?product=Thunderbird&release_channel=release&signature=shutdownhang%20%7C%20arena_t%3A%3AGetNonFullBinRun%20%7C%20nsThread%3A%3AShutdown%20%7C%20mozilla%3A%3Astorage%3A%3AConnection%3A%3AshutdownAsyncThread&date=%3E%3D2018-07-31T04%3A45%3A10.000Z&date=%3C2019-01-31T02%3A45%3A10.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=-date&page=1#graphs

Comment 2

[Wayne Mery (:wsmwk)]

Perhaps we'll be adding shutdownhang | nsThread::Shutdown | nsThreadManager::Shutdown (bug 1526127) as the version 68 equivalent signatures, because the signatures cited so far for this bug are all v60

Comment 3

[Wayne Mery (:wsmwk)]

https://support.mozilla.org/en-US/questions/1273402 google oauth?

Comment 5

[Wayne Mery (:wsmwk)]

Adding signature from bug 1526127

Comment 6

[Wayne Mery (:wsmwk)]

For version 78, only remaining signature is shutdownhang | nsThread::Shutdown | nsThreadManager::Shutdown, and still a topcrash.

Steady crash rate for last 6 months despite multiple password prompts being gone (bug 1606711), although that's not a specific cause it might have contributed to user confusion.

Comment 7

[Ulf Zibis]

Fortunately version 78 is available from Ubuntu repository since some weeks. The update didn't help. TB still crashes on shutdown, see:
Crash ID: bp-8ebffcf3-cc81-4c47-88e1-793c90210320

Comment 8

[gene smith]

(In reply to Ulf Zibis from comment #7)

Fortunately version 78 is available from Ubuntu repository since some weeks. The update didn't help. TB still crashes on shutdown, see:
Crash ID: bp-8ebffcf3-cc81-4c47-88e1-793c90210320

78.7.1 from ubuntu repo shuts down OK for me with no crash. FWIW, home-built daily for me crashes on shutdown at, I would guess, 80% of the time,
but I just started and stopped 78.7.1 at least 6 times with no crash.
But I rarely run the repo verion so maybe it has to be running for a while to crash on shutdown?

Comment 9

[Ulf Zibis]

See also bug 1524247.

Comment 10

[Ulf Zibis]

(In reply to Ulf Zibis from comment #9)

See also bug 1524247.

Oops, I meant bug 1346060.

Comment 14

[Wayne Mery (:wsmwk)]

Frank, with version 115.5.2, do you still see the issue you mention in bug 1798108 ?

Comment 15

[Frank Gadegast]

Can't tell. I'm still on version 102.15.1, because 115.x.x has to many other bugs, that are'nt fixed yet.

But heh ... it's easy to replicate on any MacOS:

Set a master password, restart TB, don't enter a password, when asked and quit TB from the menu.
Then try to restart it (it won't, because the process is still running in the background and need to be kill manually via terminal).

Comment 16

[Wayne Mery (:wsmwk)]

shutdownhang | nsThread::Shutdown | nsThreadManager::Shutdown crash signature is gone after version 91.13.0

But there are still a few user comments about password for other signatures, primarily:

• Bug 1869297 - Shutdown crash due to "Empty Trash on Exit" for inactive account - shutdownhang | mozilla::SpinEventLoopUntil | nsThread::Shutdown | nsThreadManager::ShutdownNonMainThreads
• Bug 1843744 - Crash in mozilla::dom::workerinternals::RuntimeService::CrashIfHanging shutting down Thunderbird (exit/quit)

Comment 17

[Wayne Mery (:wsmwk)]

This issue might include signature [@ shutdownhang | mozilla::SpinEventLoopUntil | nsThread::WaitForAllAsynchronousShutdowns | nsThreadManager::ShutdownNonMainThreads ] which is current #1 for beta. Increased significantly since ~124.0b4

Comment 19

[Wayne Mery (:wsmwk)]

I had closed the profiler tool in developers, daily build bp-cddec85e-45ee-4029-8400-54cf60250605

Comment 20

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

I just got this crash while having the "Enter credentials for [e-mail] on imap.gmail.com" window opened and left for more than 5 minutes(while I was working on another screen and on another application) on the latest Daily 144.0a1(20250902104421) with macOS 15.6.1

Here is my crash report: https://crash-stats.mozilla.org/report/index/505975e2-4eeb-48e2-9ca6-5e5630250903#tab-details

Comment 21

[Wayne Mery (:wsmwk)]

Bug 1783573 was fixed 2025-10-21 build, 146.0a1. I haven't tested nightly, where crash rate is only a couple per week. We need beta 146 to check for a positive impact where the crash rate is at least 40 per week.

And crashes are still seen on nightly, for example build 2025-10-26 bp-259ba90b-ea75-48af-8fa3-0cf960251101.

Comment 22

[Wayne Mery (:wsmwk)]

I got bp-d061ee60-2205-423b-8847-deddd0251121 with 146.0b2 when attempting to shutdown after failed login because the server name was wrong.

No apparent change in beta crash rate, at least up to 146.0b2. I've commented in Bug 1783573.