New issue
Advanced search Search tips

Issue 868495 link

Starred by 3 users
Status: Fixed
Owner: ----
Closed: Aug 7
Cc:
vamshi.kommuri@chromium.org
clemensh@chromium.org
adamk@chromium.org
titzer@chromium.org
dschuff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

WebAssembly baseline compiler is disabled by default on 70.0.3504.0

Reported by johnnyp...@gmail.com, Jul 27 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
Hello, it looks like that now WebAssembly baseline compiler is disabled by default on 70.0.3504.0 version. Previous version 69.x had a bing performance improvement for WebAssembly users, but it completely gone with new 70.0.3504.0 version.

What is the expected behavior?

What went wrong?
With 69.x startup time for our app was about 1 sec, but with 70.0.3504.0 it takes again about 7-8 seconds to run webassembly code.

Did this work before? Yes 69

Does this work in other browsers? Yes

Chrome version: 67.0.3396.99  Channel: n/a
OS Version: OS X 10.13.2
Flash Version:

Comment 1 by vamshi.kommuri@chromium.org, Jul 30

Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Needs-Feedback Needs-Triage-M67
Thanks for filing the issue!

@Reporter: Could you please provide any sample test file/URL which helps us to triage the issue further in a better way. Any further inputs from your end may be helpful.
Note: In reported version 67.0.3396.99 the flag #enable-webassembly-baseline isn't available.

Comment 2 Deleted

Project Member

Comment 3 by sheriffbot@chromium.org, Jul 30

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by johnnyp...@gmail.com, Jul 30 

Could you please handle console log here https://evgeny-nadymov.github.io/telegram-react/
To measure WebAssembly compile performance I check time difference between 'start instantiateWasm' and 'finish instantiateWasm' console outputs.

Steps to reproduce this issue on my side:
CASE 1:
1) run link on latest 70.0.3507.0 build
2) check that time difference between 'start instantiateWasm' and 'finish instantiateWasm' about 10 seconds
3) go to chrome://flags and switch 'WebAssembly baseline compiler' from Default to Enabled
4) check that time difference between 'start instantiateWasm' and 'finish instantiateWasm' about 1 second
5) so, 'WebAssembly baseline compiler' is disabled by default
CASE 2:
1) run link on 69.0.3483.0 build
2) check that time difference between 'start instantiateWasm' and 'finish instantiateWasm' about 1 second
3) go to chrome://flags and check that 'WebAssembly baseline compiler' at Default state
4) so, 'WebAssembly baseline compiler' is enabled by default

I think that all this about  Issue 827497 . Liftoff was enabled by default for 69.x build and disabled again for 70.x build.

Comment 5 by johnnyp...@gmail.com, Aug 1 

This issues was fixed with Chrome 70.0.3508.0

Comment 6 by hablich@chromium.org, Aug 7

Status: Fixed (was: Unconfirmed)
Thanks for checking.

Comment 7 by johnnyp...@gmail.com, Aug 7 

I'm sorry but this bug is present again with 70.0.3515.0. You need manually enable 'WebAssembly baseline compiler' to get default performance improvements from version 69.x

Comment 8 by clemensh@chromium.org, Aug 7

Cc: clemensh@chromium.org
Components: -Blink>JavaScript Blink>JavaScript>WebAssembly
Note that on the dev and canary channels, we are still running a finch experiment where Liftoff is enabled or disabled for a certain percentage of users. This is to ensure that both configurations run stable. As long as you use the default setting, you can be in any of these groups whenever you open a new tab.

Comment 9 by johnnyp...@gmail.com, Aug 7 

Thank you for explanation. So, it's not a bug.
►

Sign in to add a comment