New issue
Advanced search Search tips

Issue 862210 link

Starred by 6 users

Issue metadata

Status: Fixed
Owner:
Closed: Aug 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Webassembly is taking 5-10 seconds to do initial load when it renders instantly on Firefox.

Reported by step...@upside.com, Jul 10

Issue description

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

Steps to reproduce the problem:
1. Go to https://agitated-tesla-9f4163.netlify.com/ in chrome
2. Count till the loading... turns into a text area.

What is the expected behavior?
That it doesn't take 5+ seconds to instantiate the webassembly binary.

What went wrong?
Im really not sure why theres this vastly different amount of time between firefox and chrome. This is not a cached complication issue as its the first time ive gone to this page on both browers.

Source Code
https://github.com/trashhalo/otto-web

Did this work before? N/A 

Chrome version: 67.0.3396.99  Channel: stable
OS Version: OS X 10.13.3
Flash Version:
 
Labels: Needs-Triage-M67
Components: -Blink Blink>JavaScript>WebAssembly
Cc: vamshi.kommuri@chromium.org
Labels: Needs-Bisect Triaged-ET
Status: Untriaged (was: Unconfirmed)
Thanks for filing the issue!

Able to reproduce the issue on reported chrome version 67.0.3396.99 using Mac 10.13.1. As the issue seems to be fixed in latest canary 69.0.3488.0 marking it as Untriaged and adding Needs-bisect label. Will update the bisect info soon...
Labels: -Needs-Bisect M-69 FoundIn-69 Target-69 OS-Linux
++ to comment#3: Tried bisecting the issue further in order to check the version in which the fix has landed, later after checking few chrome versions between 67.0.3396.99 and 69.0.3488.0, realised that the issue seemed to have inconsistent behaviour i.e., it's still reproducible on latest canary 69.0.3488.0(...Attaching the screen cast for reference). 

Our observations:
=================
* Checking on a fresh profile for the first time reproduces the issue then if tried checking the same by opening another tab, the issue isn't seen i.e., web assembly is rendered instantly. Hence considering it as Non-Regression as this behaviour is seen from M60(60.0.3112.0) & removing Needs-Bisect label. Adding appropriate labels and requesting some one from Dev team to have a look into this issue for further inputs.
Note: Issue is not seen on Windows.

Thanks!
862210.mp4
323 KB View Download
Owner: ahaas@chromium.org
Status: Assigned (was: Untriaged)
Andreas, is it possible that this is somehow related to streaming compilation or similar machinery?
Status: Fixed (was: Assigned)
I think this issue was fixed by the introduction of our new WebAssembly baseline compiler Liftoff.

Sign in to add a comment