1244711 - AsyncShutdown timeout: "SessionFile: Finish writing Session Restore data"

Status: RESOLVED DUPLICATE of bug 1251347

(Firefox :: Session Restore, defect)

Description

[Georg Fritzsche [:gfritzsche]]

This bug was filed from the Socorro interface and is 
report bp-9c6840c6-5e1e-45ad-b40c-602c42160201.
=============================================================

Comment 1

[Georg Fritzsche [:gfritzsche]]

Heads-up.

Comment 2

[David Teller [:Yoric] - still alive but not very active]

Yeah, this one has been around forever. I guess someone needs to handle this, and this might as well be me.

I'm just very, very demotivated by Session Restore.

Picking, tentatively.

Comment 3

[Ada [:adalucinet]]

Just hit this crash on a Mac OS X 10.9.5 machine while performing the following steps:

1. Launch Nightly from 2015-12-01 with a clean profile.
2. Follow the steps in order to launch a new Hello conversation window (no need to join the conversation from a different PC/profile/browser)
3. Apply updates to the latest Nightly.

Actual results:
bp-d2eedba9-b7c7-4e58-a080-d37782160203
bp-dd01d7a9-9b2b-474e-b785-209352160203
bp-679c9a94-de7f-4861-b5e1-99cfc2160203

Hope it helps! and let me know if I can help more!

Comment 4

[David Teller [:Yoric] - still alive but not very active]

Is this reproducible?

Comment 5

[Ada [:adalucinet]]

(In reply to David Rajchenbach-Teller [:Yoric] (please use "needinfo") from comment #4)
> Is this reproducible?

Yes, it is - every time I follow the steps mentioned in comment 3.
A crash report from today: bp-5a08939d-3e8d-4523-a69d-1ca5f2160204

Terminal output when the crash occurs:
*************************
JavaScript error: resource://gre/modules/PerformanceStats.jsm, line 492: Error: forget() called twice
WARNING: At least one completion condition is taking too long to complete. Conditions: [{"name":"Media shutdown: blocking on media thread","state":"(none)","filename":"/builds/slave/m-cen-m64-ntly-000000000000000/build/src/dom/media/MediaManager.cpp","lineNumber":1600,"stack":"Media shutdown"}] Barrier: profile-before-change
JavaScript error: chrome://loop/content/modules/MozLoopPushHandler.jsm, line 73: NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIWebSocketChannel.asyncOpen]
FATAL ERROR: AsyncShutdown timeout in profile-before-change Conditions: [{"name":"Media shutdown: blocking on media thread","state":"(none)","filename":"/builds/slave/m-cen-m64-ntly-000000000000000/build/src/dom/media/MediaManager.cpp","lineNumber":1600,"stack":"Media shutdown"}] At least one completion condition failed to complete within a reasonable amount of time. Causing a crash to ensure that we do not leave the user with an unresponsive process draining resources.
[Parent 3254] ###!!! ABORT: file /builds/slave/m-cen-m64-ntly-000000000000000/build/src/dom/media/MediaManager.cpp, line 1600
[Parent 3254] ###!!! ABORT: file /builds/slave/m-cen-m64-ntly-000000000000000/build/src/dom/media/MediaManager.cpp, line 1600

Comment 6

[David Teller [:Yoric] - still alive but not very active]

Alexandra, your crashes are for an unrelated bug. You should find a new report for "Media shutdown: blocking on media thread", with the STR and crash reports.

Comment 7

[Ada [:adalucinet]]

(In reply to David Rajchenbach-Teller [:Yoric] (please use "needinfo") from comment #6)
> Alexandra, your crashes are for an unrelated bug. You should find a new
> report for "Media shutdown: blocking on media thread", with the STR and
> crash reports.

Thanks for your input and sorry for the noise! Logged bug 1245863 for the mentioned issue.

Comment 8

[David Teller [:Yoric] - still alive but not very active]

No problem. Next time, look in Metadata at the field AsyncShutdownTimeout. It will give you more details about the actual crash.

Comment 9

[Robert Kaiser]

Looks to me like this is another bug 1248489 signature actually.