New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 724398 link

Starred by 5 users

Issue metadata

Status: Duplicate
Merged: issue 696126
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: 1
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

WebGL broken on Samsung Galaxy Tab S2 by update

Reported by s...@timespace.co, May 19 2017

Issue description

Example URL:
http://madebyevan.com/webgl-water/

Steps to reproduce the problem:
1. Notice that WebGL is still working on a Samsung Galaxy Tab S2 in version 52.0.2743.98 (either in Chrome or Android System Webview)
2. Update to version 58.0.3029.83
3. Notice that part of the view is clipped

What is the expected behavior?
The WebGL content should be shown without clipping

What went wrong?
See attached picture, above is an device that hasn't been updated yet and below one that has.

But we have multiple devices of the same model and WebGL broke in all of them after the update.

WebGL works as expected on a Nexus 7 tablet and Nexus 6P phone even after the update.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes 52.0.2743.98

Does this work in other browsers? Yes

Chrome version: 58.0.3029.83  Channel: stable
OS Version: 6.0.1
Flash Version: 

The problem occurs both in Chrome and Android System Webview with the same version numbers
 
samsung webgl.jpg
5.2 MB View Download
Components: -Blink Internals>GPU>VendorSpecific

Comment 2 by enne@chromium.org, May 19 2017

Cc: chrishtr@chromium.org weiliangc@chromium.org osh...@chromium.org junov@chromium.org
Components: -Internals>GPU>VendorSpecific Internals>Compositing Blink>Compositing
EstimatedDays: 1
Status: Available (was: Unconfirmed)
I disagree that this vendor specific.  This seems like a compositing bug, possibly related to device scale.  It could be something wrong in Blink or wrong in cc, I'm not sure.

Comment 3 by enne@chromium.org, May 19 2017

Cc: kainino@chromium.org
 Issue 723590  has been merged into this issue.

Comment 4 by kbr@chromium.org, May 19 2017

Components: Blink>WebGL

Comment 5 by kbr@chromium.org, May 20 2017

Labels: -Type-Bug Type-Bug-Regression
Owner: kainino@chromium.org
Kai said he could start investigating this next week.

Comment 6 by kbr@chromium.org, May 20 2017

Status: Assigned (was: Available)
Note that it looks like this is affecting multiple kinds of Android devices and, in particular, Three.js users per https://github.com/mrdoob/three.js/issues/11368 .

Comment 7 by m...@playcanvas.com, May 23 2017

We (PlayCanvas) have various users reporting on same issue:
https://github.com/playcanvas/engine/issues/859#issuecomment-303170743
https://forum.playcanvas.com/t/issues-with-playcanvas-builds-on-latest-android-chrome-build-58-0-3029-83-in-redmi-note-4/4035

This has been clearly a regression issue when Chrome 58 got introduced.
Mergedinto: 696126
Status: Duplicate (was: Assigned)
Able to reproduce on Redmi Note 3.

Looks like  issue 696126 .

Comment 9 by m...@playcanvas.com, Jun 23 2017

More users are reporting of such problem.
This is a !critical! bug for WebGL content.

Comment 10 by zmo@chromium.org, Jun 23 2017

See  crbug.com/696126 . This is already fixed.

Sign in to add a comment