Bug 43034
| Summary: | Web Inspector: [JSC] debugger tests are flaky | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Pavel Podivilov <podivilov> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ggaren, loislo, mark.lam, mrobinson, oliver, pfeldman, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Pavel Podivilov
WebInspector.parsedScriptSource can be called before WebInspector.debuggerWasEnabled causing all scripts to be cleared in frontend.
The reason is that setTimeout callbacks firing order is not guaranteed for timers with different nesting levels.
In InspectorController::enableDebuggerFromFrontend InspectorFrontend::debuggerWasEnabled is called synchronously (with nesting level > 1), and ScriptDebugServer::recompileAllJSFunctionsSoon is called asynchronously (with nesting level = 1).
This may lead to WebInspector.parsedScriptSource being called before WebInspector.debuggerWasEnabled.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Martin Robinson
So this is only an issue on GTK+? What can we do to fix it for GTK+ or improve the test so that it runs on GTK+ as well?
Pavel Podivilov
Actually it's not related to GTK. It's a JSC issue.
So the test is potentially flaky on any platform, but for some reason it fails only on GTK.
Brian Burg
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests.
Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk.