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

Issue 629751 link

Starred by 3 users
Status: Archived
Owner: ----
Closed: Apr 2017
Cc:
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Abnormally long page loads (30s) for no apparent reason

Reported by samh1...@gmail.com, Jul 20 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Example URL:

Steps to reproduce the problem:
I'm experiencing this issue in a local closed-source project I'm building, so unfortunately I can't give any steps to reproduce. I'm happy to set up an ngrok tunnel and coordinate a time if anyone wants to take a look though, as this is pretty serious.

What is the expected behavior?

What went wrong?
For some reason, loading my Meteor project takes 30 seconds. It starts loading quickly, then there's a huge gap, but no indication of any particular file taking a long time. (see attachment)

In the latest Chrome stable build, this issue doesn't exist.

Did this work before? Yes Chrome 51

Chrome version: 54.0.2800.0  Channel: canary
OS Version: OS X 10.11.5
Flash Version:
Developer_Tools_-_http___samh_ngrok_io_artist_settings.png
5.1 KB View Download

Comment 1 by csharrison@chromium.org, Jul 20 2016

Components: -Internals>Network Blink>Loader
Hi samh, thanks a lot for submitting this bug.

Do you mind running an about:tracing trace, setting manual categories, and checking all the boxes on the left side? If you do this, then reproduce the bug it might shed a light on what could be going wrong.

Note: If it is really taking 30s then the technique above may run out of memory. If this happens, just reproduce again deselecting some boxes that may not be relevant (i.e. gpu).

Removing Internals>Network for now because this seems like a more general loading issue.

Comment 2 by durga.behera@chromium.org, Jul 21 2016

Cc: durga.behera@chromium.org
Labels: Needs-Feedback
samh1974@ : Could you please update the thread as per the above comment # 1.

Comment 3 by samh1...@gmail.com, Jul 25 2016 

The about:tracing page is blank in Canary due to a JS error:

tracing.js:707 Uncaught ReferenceError: Polymer is not defined(anonymous function) @ tracing.js:707

Comment 4 by csharrison@chromium.org, Jul 26 2016 

Ah sorry, that is a current bug in tracing. See  issue 630926 , which should hopefully be fixed soon.

Comment 5 by samh1...@gmail.com, Jul 26 2016 

😆

No problem. I'll come back to this issue later when tracing works again. BTW, if I should be testing with a build other than Canary, let me know.

Comment 6 by csharrison@chromium.org, Jul 26 2016 

If you can repro the issue on other channels, that would work too. Canary is not necessary.

Comment 7 by samh1...@gmail.com, Jul 28 2016 

Tracing is working in Canary now! Attaching trace.
trace.json.gz
1.7 MB Download

Comment 8 by csharrison@chromium.org, Jul 28 2016 

Woah this is extremely weird. I'm seeing a 27 second long period of HTMLScriptRunner::executeScriptsWaitingForLoad, which eventually ends up running modules.js?hash=55591fa6ba16bd58f2599b3aee977ea06e00f96a

Which categories did you use for the trace?
Project Member

Comment 9 by sheriffbot@chromium.org, Aug 5 2016

Labels: -Needs-Feedback Needs-Review
Owner: durga.behera@chromium.org
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 10 by pasko@chromium.org, Aug 5 2016

Labels: -Pri-2 -Needs-Review Needs-Feedback Pri-3
Owner: ----
samh1974:

We would like to know more what's happening in HTMLScriptRunner::executeScriptsWaitingForLoad. Can you enable more categories in tracing until something non-trivial pops up?

Also for a more isolated experiment, please disable the "Redux DevTools" extension.

Minified testcase would be nice.

Comment 11 by csharrison@chromium.org, Aug 16 2016 

ping samh. Note you could also run a timeline analysis with devtools to give you more insight into the Javascript code. However, it looks like this might be a logic error in some of the JS in your project.

If you could post a URL that reproduces we can also help more.

Comment 12 by kenjibaheux@chromium.org, Apr 10 2017

Status: Archived (was: Unconfirmed)
Closing given that we are not able to repro and haven't heard back from the reporter. Please chime in if this still is an issue and provide additional details per comments #11,10,8.
►

Sign in to add a comment