Bug 135779
| Summary: | Web Inspector: re-opening the inspector after it has crashed takes a very long time | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brian Burg <burg> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | graouts, inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 147066 | ||
Brian Burg
Joe suggested that this waiting may be for a lock that wasn't released when the process crashed.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/17966159>
Joseph Pecoraro
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.