New issue
Advanced search Search tips

Issue 604663 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Oct 31
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: Janky scrolling in sources panel

Reported by maiti...@gmail.com, Apr 19 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36

Steps to reproduce the problem:
1. Open Developer Tools 
2. Click On Sources Tab
3. Select Html file on left
4. Scroll the HTML file content

What is the expected behavior?
It should not get stuck

What went wrong?
While Scrolling Html File Code in Sources Tab, whole Developer tools gets stuck and after a minute I get Page Unresponsive alert with 2 options "Kill" & "Wait".
If i wait then again after a minute I get the same alert

Did this work before? Yes Till 2 weeks back it was working

Chrome version: 50.0.2661.75  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

Removed all the system files create by google chrome and did a fresh installation. Not just me but everyone in my organisation is having this issue
 
GoogleChromeDeveloperToolsError.png
225 KB View Download

Comment 1 by allada@chromium.org, Apr 25 2016

Labels: Needs-Feedback
This may be caused from the hardware of the computer you are using. Can you please tell me how much ram, cpu, and graphics info?

Also can you please try this with no plugins/extensions and see if it still happens?
Components: Platform>DevTools>Editing
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: DevTools: Janky scrolling in sources panel (was: Developer Tools Stuck)
We have perf issues when scrolling in Sources. 

we set scroll top and left at different times and force a layout between them. that's bad. we should set them at the same time, and force our layout before any of that.

Then we have a scroll handler that runs right after our wheel handler and repeats work. It should no-op if the wheel handler just ran int that frame.

lastly, the update layer tree is huge. that would be fixed by using transforms to do viewporting, instead of positioning, but that's a codemirror change and probably a lot harder than it looks.
scrolling-sources-panel-TimelineRawData-20160428T174016.json
3.3 MB View Download
Screen Shot 2016-04-28 at 5.41.44 PM.png
84.7 KB View Download
Components: Platform>DevTools>Authoring
Owner: einbinder@chromium.org
Status: Archived (was: Assigned)
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix.

Sign in to add a comment