New issue
Advanced search Search tips

Issue 795271 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 668398
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Devtools sources panel, live-edit save takes > 30s to complete

Reported by ajizzleb...@gmail.com, Dec 15 2017

Issue description

Chrome Version       : 63.0.3239.108
OS Version: 10.0
URLs (if applicable) : https://www.google.co.uk/
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:
 Chrome v62: OK



What steps will reproduce the problem?
1. Open dev tools on a site with some scripts ie Google.com (ss attached)
2. Open any JS file in the sources panel (no work spaces..)
3. Add a breakpoint.
4. Make a cursory edit to the script (breakpoint greys out as expected for live-edit) and save the change (star next to file name on tab disappears as expected on save).
5. Break point returning to full blue (indicating save completion) will take >30s, sometimes more.


What is the expected result?

Saving should be, and previously was, almost instantaneously completed.


What happens instead of that?

Saving takes > 30s. 


Please provide any additional information below. Attach a screenshot if
possible.

Tested in Canary, exists there also. Tested in Chrome v62 and bug was not apparent. Basically means I can't debug with dev tools..

Only seems to happen in files with > 1000 lines.

The above steps to follow were done on the google.com site, on the first minified JS file in the sources file navigator. Screenshot is attached. 

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36



 
Dev_tools_live_edit_bug_SS.png
223 KB View Download
Also (obvs) tried on several machines with same version of Chrome, tried uninstalling and re-installing, tried with multiple combinations of dev tools settings, bug still apparent..

Comment 2 by gov...@chromium.org, Dec 15 2017

Cc: pfeldman@chromium.org
Components: Platform>DevTools

Comment 3 by gov...@chromium.org, Dec 15 2017

Labels: Needs-Triage-M63
Can you give us a performance trace of DevTools? You can open up DevTools on DevTools by undocking DevTools and then doing Ctrl/Cmd + Shift + i. Then you can take a performance recording and then save it as a json and attach it. That would be very helpful. Thanks.
As requested, performance recording of Dev Tools during save. Carried out on Google.com script as in screenshot above.
live_edit_save_bug_Profile-20171218T142930.zip
10.0 MB Download
Apologies, had to zip up the recording as it is 181MB... And attachment upload limit is 10MB
Labels: -Pri-3 M-65 Triaged-ET OS-Linux OS-Mac Pri-2
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #63.0.3239.108 and latest canary #65.0.3298.3.
This is a non-regression issue as it is observed from M50 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!
Great, thank you.

Comment 9 by alph@chromium.org, Dec 20 2017

Owner: kozy@chromium.org
Status: Assigned (was: Untriaged)

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

Mergedinto: 668398
Status: Duplicate (was: Assigned)

Sign in to add a comment