crash in shutdownhang | NtUserGetMessage | NtUserGetMessage | NtUserGetMessage | WaitForCompletionMessage | DocumentPropertiesWThunk

RESOLVED FIXED

Status

defect
--
critical
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: wsmwk, Unassigned)

Tracking

({crash, topcrash-thunderbird})

Thunderbird Tracking Flags

(thunderbird53 wontfix, thunderbird54 fixed, thunderbird55 fixed)

Details

(Whiteboard: [tbird topcrash], crash signature, URL)

Comment 1

3 years ago
Just observed this in Firefox too. Might be useful to check the firefox crash comments.
I asked it to quit (Hamburger->Power button) its last window with 10 tabs and I got this.
Not sure what the cause is.
(Reporter)

Comment 3

3 years ago
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #0)
> #20 crash for 38.5.1
> bp-0fed8fb4-0e20-4226-a56a-db49c2160121.
> 
> none of the crash comments seem particularly helpful
> https://crash-stats.mozilla.com/search/
> ?signature=~DocumentPropertiesWThunk&date=%3E2016-01-01&date=%3C2016-01-
> 27&user_comments=~a&product=Thunderbird&_facets=signature&_columns=date&_colu
> mns=signature&_columns=version&_columns=build_id&_columns=platform&_columns=u
> ser_comments&_columns=email#crash-reports
> 
> Earliest crash might be 37.0b1 bp-6b60d864-ad43-4373-963d-703e32150824

bp-b9feaa8a-761c-4c5e-8a68-d8f5f2160401 38.1.0


Most common themes seem to be...
printing: bp-099dc272-54f0-4ff5-a392-1f68b2160602 bp-e65d548f-eaa5-42e9-b07a-da23c2160830 bp-64e482cb-4ae2-4448-87f2-5c0682160529 bp-40e7123e-2bf0-4bed-a8fb-d5ea52160401
after (or "while") restarting from update or addon change : bp-351fea2c-ceb6-4cb3-ae40-7e1f52160723 bp-40f788e9-72e7-4078-86ac-e664e2160710 bp-90bdd0c0-63b6-4fcc-8727-3ddd22160708

Updated

2 years ago
See Also: → 1152353
We haven't seen this crash in FX54b1 or 2 and it happened over a hundred times in the 53 counterparts, so I think we can safely say that the fix in bug 1152353, has sorted this.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.