[Webkit-unassigned] [Bug 135779] Web Inspector: re-opening the inspector after it has crashed takes a very long time

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Aug 11 13:56:45 PDT 2014


--- Comment #2 from Joseph Pecoraro <joepeck at webkit.org>  2014-08-11 13:56:56 PST ---
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.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list