Issue 156631 in chromium: High CPU usage with Developer Tools opened

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Feature-DevTools Pri-2 Via-Wizard Type-Bug OS-Mac

New issue 156631 by andrew.r...@gmail.com: High CPU usage with Developer
Tools opened
http://code.google.com/p/chromium/issues/detail?id=156631

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.4
(KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4

Steps to reproduce the problem:
1. Open page http://people.iola.dk/olau/flot/examples/basic.html
2. Right click on the chart and select "Inspect Element"
3. In the inspector click on the canvas element so the chart is highlighted
4. Press Cmd+Tab to switch to another window or program

What is the expected behavior?
Normal CPU usage

What went wrong?
Chrome CPU usage is quite high. I can see 2 Chrome processes, each consumes
30-35% of CPU, which leads to high CPU temperature (see attached
screenshot).

Did this work before? Yes Not quite sure, but this problem is very recent...

Chrome version: 22.0.1229.94 Channel: stable
OS Version: OS X 10.8.2

It seems to me, that this happens not only on the pages with canvas, but on
majority of pages with bunch of DOM elements. There is no such problem in
Safari.

Attachments:
chrome_trace.zip 2.3 MB
Screen Shot 2012-10-18 at 18.51.01 .png 384 KB

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: ca...@chromium.org

Comment #1 on issue 156631 by pfeld...@chromium.org: High CPU usage with

Developer Tools opened
http://code.google.com/p/chromium/issues/detail?id=156631

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Fixed
Labels: -OS-Mac Area-WebKit

Comment #2 on issue 156631 by ca...@chromium.org: High CPU usage with

Developer Tools opened
http://code.google.com/p/chromium/issues/detail?id=156631

Fixed upstream as of r129511, rolled into chromium at r158652.
See https://bugs.webkit.org/show_bug.cgi?id=97466 for details.

[chro...@googlecode.com]

Updates:
Labels: Merge-Requested Mstone-23

Comment #3 on issue 156631 by ca...@chromium.org: High CPU usage with

Developer Tools opened
http://code.google.com/p/chromium/issues/detail?id=156631

We probably want to merge that into m23, as we started using Inspector
Overlay (a DOM page) for highlighting of the selected node in m23, which
somewhat increases the overhead of repeatedly updating the overlay.
There are two fixes: http://trac.webkit.org/changeset/129511 and
http://trac.webkit.org/changeset/129772 and these have been on canary and
dev channel for more than 3 weeks without issues.

[chro...@googlecode.com]

Updates:
Labels: -Merge-Requested Merge-Approved

Comment #4 on issue 156631 by kar...@google.com: High CPU usage with

Developer Tools opened
http://code.google.com/p/chromium/issues/detail?id=156631

ok

[chro...@googlecode.com]

Updates:
Labels: -Merge-Approved Merge-Merged

Comment #5 on issue 156631 by ca...@chromium.org: High CPU usage with

Developer Tools opened
http://code.google.com/p/chromium/issues/detail?id=156631

Merged to m23 as http://trac.webkit.org/changeset/132049 and
http://trac.webkit.org/changeset/132048