New issue
Advanced search Search tips

Issue 754357 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 754356
Owner: ----
Closed: Aug 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome 60, turning on wasm flag gives visual glitches in emscripten converted C++ rendering code

Reported by sarves...@gmail.com, Aug 10 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. We have our own app - Farmville2 which runs over scaleform through emscripten in browser( without flash , using wasm/asm instead)
2. The game used to work well on Chrome 59 with wasm flag turned on
3. With Chrome 60 with flag turned on there are visual glitches and slower performance

What is the expected behavior?
This used to work well on Chrome 59. Did Chrome 60 introduce many changes in the behavior of this flag?

What went wrong?
There are visual glitches, sometimes we are not able to load, and the performance is perceivably slower, we are forced to run without the flag being turned on - the default behavior I assume in course of time would be the flag would remain on which will break the game, this would prevent us from using the optimizations of wasm.

Did this work before? Yes Chrome 59

Chrome version: 60.0.3112.90  Channel: stable
OS Version: 10
Flash Version:
 
Mergedinto: 754356
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment