Closed Bug 1197214 Opened 10 years ago Closed 8 years ago

attempted shutdown then crash in shutdownhang | libsystem_kernel.dylib@0x16166

Categories

(Thunderbird :: General, defect)

42 Branch
Unspecified
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: Pike, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-914ec288-12f9-4c0d-956a-aa6d12150821. ============================================================= Thunderbird/42.0a2 20150820004006 consumes 100% CPU, and when trying to shut it down, it crashes. Happened twice today.
See Also: → 1192778
Axel, still seeing this?
Flags: needinfo?(l10n)
Summary: crash in shutdownhang | libsystem_kernel.dylib@0x16166 → attempted shutdown then crash in shutdownhang | libsystem_kernel.dylib@0x16166
Version: unspecified → 42
9-16 is the latest in my list, https://crash-stats.mozilla.com/report/index/8d23e692-75b7-414c-9f23-4ccde2150917, but there are newer ones on crashstats for Tb 42, too.
Flags: needinfo?(l10n)
(In reply to Axel Hecht [:Pike] from comment #2) > 9-16 is the latest in my list, > https://crash-stats.mozilla.com/report/index/8d23e692-75b7-414c-9f23- > 4ccde2150917, but there are newer ones on crashstats for Tb 42, too. matches stack of original crash report 0 XUL mozilla::(anonymous namespace)::RunWatchdog(void*) toolkit/components/terminator/nsTerminator.cpp 1 libnss3.dylib _pt_root nsprpub/pr/src/pthreads/ptthread.c Ø 2 libsystem_pthread.dylib libsystem_pthread.dylib@0x4059 Ø 3 libsystem_pthread.dylib libsystem_pthread.dylib@0x3fd6 Ø 4 libsystem_pthread.dylib libsystem_pthread.dylib@0x13ec 5 libnss3.dylib libnss3.dylib@0x201cef
Bug 1199957, maybe?
I only have IMAP and NNTP accounts in thunderbird.
What's your older crash IDs. Any prior to 2015-07-14?
Flags: needinfo?(l10n)
Hard to tell. In particular because going through my crash-reports hangs thunderbird :-( I also have a ton of reasons why tb crashes, so it's a long list.
Flags: needinfo?(l10n)
Hi Axel. Have your crashes stopped? And which version are you running?
Flags: needinfo?(l10n)
Haven't seen these in a while, I'm now dogfooding the localized Daily.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(l10n)
Resolution: --- → WORKSFORME
Nice! When did it go away - with a thunderbird update? Or an OS update?
TBH, I don't know. All about:crashes shows me still is bp-f6a5d584-9273-4ef4-8ac7-055ab2160921 21/09/16 23:20 bp-fb9f2722-2f65-43c5-896a-e1ce02160918 18/09/16 16:12 bp-6b6c09d4-5002-42ef-bc98-f2aa22160830 30/08/16 14:44 bp-879b7fd7-d12a-48fa-b60f-097a02160705 05/07/16 07:12 bp-9d63cc2e-3ab0-44f5-a53e-583062160313 13/03/16 09:35 bp-c74c55e4-2e93-42d0-8167-c0c5a2160107 07/01/16 23:29 As you can see, Daily has been pretty stable on me.
(In reply to Axel Hecht [:Pike] from comment #11) >... > As you can see, Daily has been pretty stable on me. we like stability! (I also use daily) (In reply to Calum Mackay from comment #12) > My last crash for this was: > > Build ID 20161008 > > https://crash-stats.mozilla.com/report/index/c1afb0b7-7a86-46f7-984f- > e29b62161010 That claims to be a horribly old 46.0a1, so I wouldn't attach much credence to whether that indicates the problem is gone in current versions. FWIW, the most recent nightly build to crash with this signature is 20161018191444 in bp-b916a940-ee36-43dc-a571-e84202161019 from https://crash-stats.mozilla.com/signature/?product=Thunderbird&release_channel=%21release&signature=shutdownhang%20%7C%20libsystem_kernel.dylib%400x16db6&date=%3E%3D2016-07-28T12%3A09%3A14.000Z&date=%3C2016-10-28T12%3A05%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-build_id&_sort=-date&page=1 But the nightly crash rate is low, so it may be some weeks before we can say whether the problem is gone from nightly
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #13) > (In reply to Axel Hecht [:Pike] from comment > (In reply to Calum Mackay from comment #12) > > My last crash for this was: > > > > Build ID 20161008 > > > > https://crash-stats.mozilla.com/report/index/c1afb0b7-7a86-46f7-984f-e29b62161010 > > That claims to be a horribly old 46.0a1, so I wouldn't attach much credence > to whether that indicates the problem is gone in current versions. Not sure where you got that from? The above crash is from 52.0a1, as it says in the report? I must be misunderstanding, sorry…
(In reply to Calum Mackay from comment #14) > (In reply to Wayne Mery (:wsmwk, NI for questions) from comment #13) > > (In reply to Axel Hecht [:Pike] from comment > > (In reply to Calum Mackay from comment #12) > > > My last crash for this was: > > > > > > Build ID 20161008 > > > > > > https://crash-stats.mozilla.com/report/index/c1afb0b7-7a86-46f7-984f-e29b62161010 > > > > That claims to be a horribly old 46.0a1, so I wouldn't attach much credence > > to whether that indicates the problem is gone in current versions. > > Not sure where you got that from? The above crash is from 52.0a1, as it says > in the report? > > I must be misunderstanding, sorry… Thanks for pointing that out. My bad. I must have been looking at axel's https://crash-stats.mozilla.com/report/index/c74c55e4-2e93-42d0-8167-c0c5a2160107 which is 46.0a1
You need to log in before you can comment on or make changes to this bug.