[Webkit-unassigned] [Bug 237636] New: 2.35.x errors out on Ubuntu arm64

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Mar 9 00:25:30 PST 2022


https://bugs.webkit.org/show_bug.cgi?id=237636

            Bug ID: 237636
           Summary: 2.35.x errors out on Ubuntu arm64
           Product: WebKit
           Version: Other
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKitGTK
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: seb128 at debian.org
                CC: bugs-noreply at webkitgtk.org

Since the Debian package got updated to 2.35 some of the Ubuntu autopkgtests have been failing on arm64, trying to start the demo browser it seems webkitgtk is indeed buggy on that architecture

Trying with the current 2.35.90 package

$ /usr/lib/aarch64-linux-gnu/webkit2gtk-4.0/MiniBrowser 
libEGL warning: DRI3: failed to query the version
libEGL warning: DRI2: failed to authenticate

(WebKitWebProcess:1316379): Gdk-ERROR **: 07:55:56.794: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 193 error_code 1 request_code 155 (unknown) minor_code 1)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

** (MiniBrowser:1316360): WARNING **: 07:55:57.176: WebProcess CRASHED


Getting a backtrace is a bit tricky because the VM is limited in memory and it fails to complete the gdb session


Downgradeing to 2.34 the browser works fine and there is no DRI2 or 3 warnings

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220309/5b66eec4/attachment.htm>


More information about the webkit-unassigned mailing list