Issue metadata
Sign in to add a comment
|
WebGL buffer resize not working correctly on Xiaomi Snapdragon devices
Reported by
a.b...@orangegames.com,
May 17 2017
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: Open a Phaser (WebGL canvas library) game where the initial canvas size is smaller than when the game gets resized for the first time (noteable exampless: https://www.gameeapp.com/game/OsqXRuoNE and http://jewel-burst.fbrq.io/jewel-burst/index.html) What is the expected behavior? The game should be playable and take up the entire available screen size What went wrong? It appears that after resizing the Canvas that the WebGL buffer doesn't resize correctly. In console you can see the correct width and height set on the gl content, but everything outside the original size is black. The part that is correctly shown is also anchored to the bottom left. Did this work before? N/A Chrome version: 58.0.3029.83 Channel: stable OS Version: 6.0.1 MMB29M Flash Version: N.A. So far I only managed to reproduce this on Xiaomi devices with a Snapdragon chipset included on Chrome (Beta en Release). Firefox does show the game correctly without any black areas. Also; Xiaomi devices with a Mediatek chipset don't have the issue.
,
May 17 2017
Can't reproduce on Pixel. Please copy+paste the contents of chrome://gpu into a comment here. We need it in order to diagnose any GPU related issue.
,
May 18 2017
Thank you for providing more feedback. Adding requester "kainino@google.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 18 2017
Interesting. The about:gpu from #3 (Redmi 4 Prime) is an Adreno 506 running ES 3.1 and driver version 145.0 (GIT@I74772a33ad). The Redmi Note 3 is an Adreno 510, ES 3.1, driver version 139.0 (GIT@I59a6815413). For comparison, the Google Pixel has an Adreno 530 running ES 3.2, driver version 145.0 (GIT@Idb2b4cb785) and doesn't exhibit these issues. Not sure whether we have these Xiaomi devices in house.
,
May 18 2017
,
May 18 2017
It's possible that this is an issue with an esoteric hi-dpi scaling factor, or something, which would explain why it's not seen on other devices. It looks like there's a Redmi Note 3 we should be able to test on.
,
May 19 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by candr...@chromium.org
, May 17 2017