Closed Bug 1301339 Opened 9 years ago Closed 9 years ago

Annotate content shutdown hang due to nested event loop in RecvShutdown

Categories

(Core :: DOM: Content Processes, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla51
Tracking Status
firefox51 --- fixed

People

(Reporter: kanru, Assigned: kanru)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

We currently allow nested event loop to delay ContentChild::RecvShutdown which in turn might cause content process shutdown hang. This patch attempts to annotate the crash report that a shutdown hang was after we have received RecvShutdown but never reach SendFinishShutdown or the hang happened before or after RecvShutdown.
Assignee: nobody → kchen
Comment on attachment 8789304 [details] Bug 1301339 - Annotate content shutdown hang due to nested event loop in RecvShutdown. https://reviewboard.mozilla.org/r/77582/#review76122 Maybe it would be better to have one annotation, IPCShutdownState, that could be either empty, "RecvShutdown", or "SendFinishShutdown"?
Attachment #8789304 - Flags: review?(wmccloskey) → review+
(In reply to Bill McCloskey (:billm) from comment #2) > Comment on attachment 8789304 [details] > Bug 1301339 - Annotate content shutdown hang due to nested event loop in > RecvShutdown. > > https://reviewboard.mozilla.org/r/77582/#review76122 > > Maybe it would be better to have one annotation, IPCShutdownState, that > could be either empty, "RecvShutdown", or "SendFinishShutdown"? Sounds good.
Pushed by kchen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/399174fe175a Annotate content shutdown hang due to nested event loop in RecvShutdown. r=billm
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: