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

Issue 803939 link

Starred by 2 users
Status: Archived
Owner:
kozy@chromium.org
Closed: Feb 2018
Cc:
█ sc00335...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Loading my angular site with DevTools open causes it to render 20x slower

Reported by michaels...@gmail.com, Jan 19 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Open DevTools
2. Reload the application

What is the expected behavior?
The site loads and renders approximately as fast as with DevTools closed (~ 2 seconds).

What went wrong?
The site renders in upwards of 55 seconds.

Did this work before? Yes First noticed it broken in 65.0.3298.0, possibly earlier.

Chrome version: 65.0.3325.0  Channel: canary
OS Version: 10.0
Flash Version: 

I could not attach the *problematic* trace (too big), but it's here: https://chromiumdev.slack.com/files/U04RE8C68/F8VPC7RQS/trace_trace_ng5_frozen_render_devtools_open.zip

The site will render as expected if recording a Performance Profile (tested with 'Start profiling and reload page').

The application being accessed is ng 5.0.5 served via a localhost ng serve proxy.

See https://chromiumdev.slack.com/archives/C051KSB4E/p1515770696000566 onward.
trace_trace_ng5_frozen_render_devtools_closed.zip
2.0 MB Download
trace_trace_ng5_frozen_render_devtools_open_while_profiling.zip
2.6 MB Download
trace_trace_ng5_frozen_render_devtools_open.zip
16.0 MB Download

Comment 1 by michaels...@gmail.com, Jan 19 2018 

It seems the linked trace ("trace_trace_ng5_frozen_render_devtools_open.zip") *did* attach to the ticket, after all.

Comment 2 by sc00335...@techmahindra.com, Jan 22 2018

Cc: sc00335...@techmahindra.com
Components: -Platform>DevTools Platform>DevTools>Performance>Tracing
Labels: Triaged-ET Needs-Feedback Needs-Triage-M65
Thanks For filing the issue!!

@Reporter: Could you please attach sample file to check this issue from TE End. This would help in further triaging of the issue.

Thanks!

Comment 3 by kozy@chromium.org, Jan 22 2018

Owner: kozy@chromium.org
Status: Assigned (was: Unconfirmed)
Could you try to open DevTools settings and in Debugger section check "Disable async stack traces" checkbox and confirm that application reload is still slow?

Comment 4 by michaels...@gmail.com, Jan 22 2018 

Hi!

What additional sample file would you like me to attach? If it's an (ng) application source, the request is perfectly reasonable but I'm afraid my hands are tied: the application is closed source and I'm under an NDA.

(I had to sanitize those perf traces as it is.)

Comment 5 by michaels...@gmail.com, Jan 22 2018 

NOTE: now testing with Version 66.0.3328.0 (Canary).

@kozy, thank you for replying.

Checking "Disable async stack traces" had no effect.

Additionally, closing DevTools immediately after reloading the page also has no effect: it still loads slowly.

DevTools must be closed at the time the page reload is triggered in order to load normally.

Comment 6 by kozy@chromium.org, Jan 22 2018 

Thanks!

I took a look on traces. It looks like page load by itself took the same time with and without DevTools.

Could you describe in more details how you reload page? Do you use the reload button? If so, could you observe the same freeze if trigger page reload by clicking enter when focus inside omnibox (navigate to the current url)?

Comment 7 by kozy@chromium.org, Feb 15 2018

Status: Archived (was: Assigned)
►

Sign in to add a comment