Bug 135779 - Web Inspector: re-opening the inspector after it has crashed takes a very long time
Summary: Web Inspector: re-opening the inspector after it has crashed takes a very lon...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks: InspectorDebug
  Show dependency tree / graph
 
Reported: 2014-08-08 16:56 PDT by Brian Burg
Modified: 2016-12-13 15:39 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Burg 2014-08-08 16:56:16 PDT 
Joe suggested that this waiting may be for a lock that wasn't released when the process crashed.
Comment 1 Radar WebKit Bug Importer 2014-08-08 16:56:27 PDT 
<rdar://problem/17966159>
Comment 2 Joseph Pecoraro 2014-08-11 13:56:56 PDT 
My guess is that the inspector that crashed might have a lock on something (local storage? sql storage?) during the time it takes crash reporter to create a symbolicated stack trace, and so a new opening inspector might be blocking on access.

In order to find out what is really happening, we just need to get a quick sample of the new web process while it is trying to open the new inspector.