Long JS execution while scrolling Twitter
Reported by
duart...@gmail.com,
May 12 2016
|
|||||||
Issue descriptionChrome Version : Version 51.0.2704.36 beta-m (64-bit) Operating System and Version: Windows 10 Education URLs (if applicable) :twitter.com & ESPN.com Description of performance problem: While scrolling through twitter timeline, there is consistent lag. Initially, I thought it was my bandwidth, but then I jumped onto Microsoft Edge and the lag was non-existent, but I could simultaneously recreate the problem on the Chrome beta version. It also appears on ESPN.com -- On ESPN, I clicked through some headlines and the pages were slow to load, laggy, and kicked up my processor fans. This does not take place on IE or Edge and didn't occur prior to updating to the Beta version. Remember to attach your trace file to this bug!
,
May 13 2016
Thanks for submitting this bug with the trace. There are large (1.5 second) blocks of JavaScript executing one each frame, which would definitely produce the lag you're describing. Can you attempt in incognito mode, and see if it reproduces there? If not, which extensions do you have installed?
,
May 13 2016
I went ahead and updated from "Version 51.0.2704.36 beta-m (64-bit)" to "Version 51.0.2704.47 beta-m (64-bit)." The problem persisted even after relaunching to the new update. I disabled all extensions and started working through each extension individually. It appears the culprit is Adblock Plus version 1.11 (https://chrome.google.com/webstore/detail/adblock-plus/cfhdojbkjhnklbpkdaibdccddilifddb?utm_source=chrome-app-launcher-info-dialog) After disabling Adblock plus, performance immediately returned to pre-beta status. No visible display lag, slow loading of pages. I've attached two logs in case that is helpful. One with adblock disabled, one with it enabled.
,
May 13 2016
Devlin, do we have a contact at ABP we could alert to this issue?
,
May 13 2016
@4 First we need to make sure it's not our fault. :) This sounds like issue 608444, which was caused by issue 606207 (+littledan). The merge for 606207 should be going into M51 soon. @duart012 - if you wanted to experiment, you could confirm whether or not you see the same lag in Chrome Canary, which has the fix for 606207. Otherwise, I'm hoping we get the update out soon. litteldan@, is there a timeline for when that will be reaching M51?
,
May 13 2016
The changes are all merged and should be in the next 51 Beta release.
,
May 17 2016
duart012, if you want a preview of the fix, it has already landed on the Canary and Dev channels. The Beta fix should be out by Wednesday.
,
May 19 2016
,
May 20 2016
Thanks all. Finally had an opportunity to test -- works great on Version 51.0.2704.54 beta-m (64-bit). Was not able to reproduce behavior from earlier beta versions. ABP among other extensions are working as intended.
,
May 21 2016
Thank you for providing more feedback. Adding requester "msrchandra@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
,
May 24 2016
@duart012 -- Thank You for the update. Marking the issue as Won't Fix as per Comment#9. Please feel free to raise a new bug if the issue again occurs. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ajha@chromium.org
, May 13 2016Labels: Needs-Feedback