Bug#1078769: libwebkit2gtk-4.1-0: libwebkit2gtk does not render or is unresponsive if run in VMware guest with 3D acceleration enabled

[Alberto Garcia]

Thanks.

One question, when you run MiniBrowser without the switch set and it
crashes, does it really have "Policy: never" here?

    "Hardware Acceleration Information": {
        "Policy": "never",
        "WebGL enabled": "Yes"
    }

On Wed, Aug 28, 2024 at 05:28:30PM -0600, Markus Hamilton wrote:
> Berto,
> 
> Sorry that I missed reading that other email but here are the results:
> 
> 
> 
> If WEBKIT_DISABLE_COMPOSITING_MODE=1 is set:
> 
> No error messages in terminal from surf, yelp or Minibrowser
> 
> 
> 
> If WEBKIT_DISABLE_COMPOSITING_MODE=1 is NOT set:
> 
> All programs always generate this message on exit:
> ** (WebKitWebProcess:3197): ERROR **: 16:46:24.424: WebProcess didn't exit
> as expected after the UI process connection was closed
> 
> yelp generates this message on startup:
> Recursion depth exceeded calculating yellow bg color. Using rgb(248,245,245)
> 
> surf - when run with a parameter like https://duckduckgo.com - generates
> this message on startup:
> Could not read style file: /home/baer/.surf/styles/default.css
> 
> surf - when run without a parameter - does not generate a message on
> startup.
> 
> MiniBrowser also does not generate a message on startup.
> It does not render its startup page, but still seems to be alive.
> I can enter about:gpu, which, to my surprise, it rendered.
> But at the end of rendering it crashed and became unresponsive.
> 
> I ran MiniBrowser again with the switch set which enabled me to copy the
> output. Here it is:
> {
>     "Version Information": {
>         "WebKit version": "WebKitGTK 2.44.2 (tarball)",
>         "Operating system": "Linux 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC
> Debian 6.1.99-1 (2024-07-15) x86_64",
>         "Desktop": "MATE",
>         "Cairo version": "1.16.0 (build) 1.16.0 (runtime)",
>         "GStreamer version": "1.22.0 (build) GStreamer 1.22.0 (runtime)",
>         "GTK version": "3.24.38 (build) 3.24.38 (runtime)"
>     },
>     "Display Information": {
>         "Identifier": "1",
>         "Type": "X11",
>         "Screen geometry": "0,0 1920x1080",
>         "Screen work area": "0,0 1920x1052",
>         "Depth": "24",
>         "Bits per color component": "8",
>         "Font Scaling DPI": "96.1259765625",
>         "Screen DPI": "48.01009246050164",
>         "VBlank type": "Timer",
>         "VBlank refresh rate": "60Hz"
>     },
>     "Hardware Acceleration Information": {
>         "Policy": "never",
>         "WebGL enabled": "Yes"
>     }
> }
> 
> I compared this output visually to the output of the crashed MiniBrowser
> when the switch is not set.
> They are identical. So the output above is not different depending on the
> switch.
> 
> My installation has only one MiniBrowser build in
> /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/ .
> Let me know if I can test anything else for you.
> 
> Markus