Bug 139364 – [GTK] Layout test inspector-protocol/debugger/setBreakpoint-dfg.html crashes.

• Component: WebKitGTK
• Status: RESOLVED FIXED

[Carlos Alberto Lopez Perez]

Created attachment 242742 [details]
GDB Backtrace for the GTK port when running the test inspector-protocol/debugger/setBreakpoint-dfg.html on r176918

Since r[176459-176503] (I was not able to identify the specific commit, only that range) the layout test inspector-protocol/debugger/setBreakpoint-dfg.html crashes on platform GTK.

The same seems to happen for platforms EFL and AppleWin

Before that it was flaky. Check 128736.

I'm attaching a GDB backtrace for port GTK on r176918

[Carlos Alberto Lopez Perez]

Maybe (just guessing, didn't tested) the revision causing the regression was r176479 (is inside the range) and it caused another regressions on the inspector. Check bug 139359.

[Carlos Alberto Lopez Perez]

Marked accordingly on the GTK expectations on https://trac.webkit.org/r176922

[Marcos Chavarría Teijeiro (irc: chavaone)]

The test is flaky since r179015 (http://trac.webkit.org/changeset/179015).

When it fails the diff is the following:

--- /home/ch01/jhbuild/src/WebKit/WebKitBuild/Release/layout-test-results/inspector-protocol/debugger/setBreakpoint-dfg-expected.txt
+++ /home/ch01/jhbuild/src/WebKit/WebKitBuild/Release/layout-test-results/inspector-protocol/debugger/setBreakpoint-dfg-actual.txt
@@ -1,18 +1,2 @@
-Debugger.setBreakpoint in DFG compiled functions.
+FAIL: Timed out waiting for notifyDone to be called

-Found breakpoint.js
-dfgWithoutInline result: 502500
-dfgWithInline result: 504500
-dfg functions warmed up
-
-Breakpoint set in notInlineable()
-Breakpoint set in inlineable()
-
-Hit Breakpoint 1!
-Removed Breakpoint 1!
-dfgWithoutInline result: 502500
-Hit Breakpoint 2!
-Removed Breakpoint 2!
-dfgWithInline result: 504500
-PASS
-

Updating test expectations on bug 143870.

[Diego Pino]

There are no references to this bug in any TestExpectations. It's probable this bug was solved at some point but it wasn't marked as closed. I'm closing this bug now. If you think this bug report is still valid, please reopen it and add an entry to TestExpectations.