100% CPU usage
Reported by
birkel...@gmail.com,
Jul 17 2017
|
||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Go to https://jsplumbtoolkit.com/community/demo/dynamicAnchors/index.html 2. Drag the boxes around for a while. Usually triggers in less than 30 seconds for me. 3. The tab goes to 100% CPU usage. Refreshing does not fix it, the tab must be closed. What is the expected behavior? Chrome keeps to a lower level of CPU usage. What went wrong? Chrome suddenly hogs a core. Did this work before? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: Debian buster/sid Flash Version: I have observed this on my Linux laptop with an integrated intel GPU as well as my Windows 10 workstation with a 1070 nvidia GPU. I cannot reproduce it in Firefox which leads me to believe that this is a problem with Chrome and not the library.
,
Jul 18 2017
This is consistently reproducible on Latest Stable#59.0.3071.115 for Mac OS X 10.13 and here is the attached trace.
,
Jul 18 2017
,
Jul 19 2017
Able to reproduce this issue on Ubuntu 14.04 and Mac OS 10.12.5 using chrome latest stable #59.0.3071.115 but not able to reproduce this issue on Windows-10. Tested this issue on older version of chrome M35-35.0.1849.0 and observed the issue is seen. Hence marking it as untriaged for further updates.
,
Jul 20 2017
,
Jul 27 2017
Weird, I can reproduce the issue in 59.0.3071.115 on Linux, the CPU % goes to 100+ and stays there even when I'm not doing anything. However, doing a trace at that point shows the renderer to be idle - perhaps the metrics are broken? I've attached a trace that I started after the CPU % was hanging around 100%, it shows the browser and renderers not doing much. I wasn't able to reproduce on 61.0.3163.13 even though it was consistent in 59. birkelund@, could you try this out in Canary/Dev channel and see if you can still repro?
,
Jul 27 2017
,
Jul 27 2017
bokan@, I cannot reproduce it on 61.0.3163.13 (Linux 64bit). The behavior you describe about the browser and renderers not doing much is exactly what I observed too on 59.0.3071.115.
,
Jul 27 2017
Ok - thanks for checking. Lets close for now since this is fixed in upcoming releases, feel free to reopen or file a new bug if you see this come up again.
,
Aug 10 2017
The NextAction date has arrived: 2017-08-10 |
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Jul 18 2017