178784 2017-10-25 05:01:01 -0700 [GTK] inspector/console/webcore-logging.html is failing 2021-06-04 19:40:20 -0700 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED P2 Normal --- 1 aboya webkit-unassigned dpino inspector-bugzilla-changes joepeck magomez oldest_to_newest 1364175 0 aboya 2017-10-25 05:01:01 -0700 The following layout test is failing on GTK. inspector/console/webcore-logging.html 1364316 1 joepeck 2017-10-25 11:07:27 -0700 Bugs like this are far more actionable when you include a link to the output / diff. 1506259 2 joepeck 2019-02-14 11:13:58 -0800 *** Bug 179174 has been marked as a duplicate of this bug. *** 1640236 3 dpino 2020-04-10 10:09:07 -0700 The test started passing after r259709, which updated test expectations after r259705. However, the test is still crashing occasionally. For instance, it crashed in GTK test build #13279 (https://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release%20%28Tests%29/builds/13279). Step "MasterShellCommand -> View LayoutTest results" should include a stacktrace, but the test is not reported as crash there. Inspecting LayoutTest stdio shows: 07:34:04.006 127258 worker/11 inspector/console/webcore-logging.html crashed, (stderr lines): 07:34:04.006 127258 Error sending IPC message: Connection reset by peer 07:34:04.006 127258 Error sending IPC message: Broken pipe 07:34:04.006 127258 Error sending IPC message: Broken pipe 07:34:04.006 127258 Error sending IPC message: Broken pipe 07:34:04.006 127258 failed to create drawable 07:34:04.006 127258 Xlib: sequence lost (0x100f1 > 0xf5) in reply type 0x0! 07:34:04.006 127258 07:34:04.006 127258 (WebKitWebProcess:34584): Gdk-ERROR **: 07:33:58.050: The program 'WebKitWebProcess' received an X Window System error. 07:34:04.006 127258 This probably reflects a bug in the program. 07:34:04.006 127258 The error was 'BadMatch (invalid parameter attributes)'. 07:34:04.006 127258 (Details: serial 241 error_code 8 request_code 148 (GLX) minor_code 34) 07:34:04.006 127258 (Note to programmers: normally, X errors are reported asynchronously; 07:34:04.006 127258 that is, you will receive the error a while after causing it. 07:34:04.006 127258 To debug your program, run it with the GDK_SYNCHRONIZE environment 07:34:04.006 127258 variable to change this behavior. You can then get a meaningful 07:34:04.006 127258 backtrace from your debugger if you break on the gdk_x_error() function.) 1767073 4 dpino 2021-06-04 19:40:16 -0700 This test, or group of tests, has been passing for the last 4000 revisions. Closing bug. Gardened in r278519.