Crash in AsyncShutdownTimeout | profile-before-change | Places Connection shutdown

NEW
Unassigned

Status

()

Toolkit
Places
P3
critical
8 months ago
12 days ago

People

(Reporter: marcia, Unassigned)

Tracking

({crash})

55 Branch
x86
Windows 7
crash
Points:
---

Firefox Tracking Flags

(firefox55 wontfix, firefox56 wontfix, firefox57 wontfix, firefox59 affected, firefox60 affected, firefox61 affected)

Details

(Whiteboard: [fxsearch], crash signature)

This bug was filed from the Socorro interface and is 
report bp-d5246b0c-a246-4853-b4ce-497330170831.
=============================================================

Seen while looking at 55 crash stats: http://bit.ly/2eHfmrw. Currently in 55.0.3 it isn't very high ranking (#45), but it didn't have a bug associated with it.

Also affects 56 and 57.
Marco, I saw profile-before-change | Places Connection shutdown in the signature. I guess this is for you!
Flags: needinfo?(mak77)
I've already seen it (I keep an eye on crash stats usually), but it's not actionable as-is.
It means Places started closing the connection, but something didn't allow that, after 1 minute async shutdown just forcibly crashed Firefox.
Unfortunately all the information in the metadata is "state":{"progress":{}}. Not really useful. There may be a bug in how we pass it, or in async shutdown itself, but I didn't find it so far and didn't have time to dig deeper.

One thing we should do, imo, is to add a circular buffer to async shutdown keeping the last N log messages, and push those along the async shutdown metadata. Async shutdown logging may help us identify what happened just before the crash.
Flags: needinfo?(mak77)
Priority: -- → P5
Marco, why did you mark it as p5?

This is impacting a lot of users on release (~100k install at least).
status-firefox55: affected → wontfix
status-firefox56: affected → wontfix
status-firefox57: affected → wontfix
status-firefox59: --- → affected
status-firefox60: --- → affected
status-firefox61: --- → affected
Flags: needinfo?(mak77)
Hm, it should have been a P3 :(
The problem here is that there's no clear cause nor solution to this problem for now, it's really cryptic.
Flags: needinfo?(mak77)
Whiteboard: [fxsearch]
Priority: P5 → P3
You need to log in before you can comment on or make changes to this bug.