Bug 188108 - [GTK] Layout tests should run with GDK_SYNCHRONIZE set
Summary: [GTK] Layout tests should run with GDK_SYNCHRONIZE set
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: Other
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-27 12:12 PDT by Michael Catanzaro
Modified: 2018-07-27 12:12 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Catanzaro 2018-07-27 12:12:52 PDT 
I'm tired of seeing useless backtraces caused by asynchronous X errors. We should run our layout tests with GDK_SYNCHRONIZE set in the environment.

STDERR: (WebKitWebProcess:110155): Gdk-ERROR **: The program 'WebKitWebProcess' received an X Window System error.
STDERR: This probably reflects a bug in the program.
STDERR: The error was 'BadAccess (attempt to access private resource denied)'.
STDERR:   (Details: serial 4583 error_code 10 request_code 130 (MIT-SHM) minor_code 1)
STDERR:   (Note to programmers: normally, X errors are reported asynchronously;
STDERR:    that is, you will receive the error a while after causing it.
STDERR:    To debug your program, run it with the GDK_SYNCHRONIZE environment
STDERR:    variable to change this behavior. You can then get a meaningful
STDERR:    backtrace from your debugger if you break on the gdk_x_error() function.)

Note GDK will need to be added to the environment prefix whitelist that was added in bug #188002