Skip to content

Investigation of Chrome 151 rendering regression on Xclipse GPUs #1363

Description

@miguelblix99

(Specifically newer Samsung devices using Exynos chip (e.x European market Samsung S24 or Samsung A56 5G)

Encountered a rendering regression in Chrome version 151 on Android devices using Samsung Xclipse GPUs. WebGL content

Google has acknowledged the regression and implemented an ANGLE workaround that disables robust buffer access on Xclipse GPUs:
https://chromium-review.googlesource.com/c/angle/angle/+/8265428

The fix was backported to Chrome 152:
https://chromium-review.googlesource.com/c/angle/angle/+/8276357

Even though this will get fixed automagically as version 152 is fully rolled out it would be beneficial to understand what could trigger this in Heaps. If its rendering operations, shader patterns, buffer layouts, or instancing behavior make the issue reproducible.

The original issue thread on google https://issuetracker.google.com/issues/547065826

The visual issue is reproducible in the official heaps demos on said devices.
It is very prominent with Base2D Demo and also in the Base3D Demo (slightly harder to see but only one triangle being shaded on the cube).

Image Image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions