UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36

Steps to reproduce the problem:
1. Open any url (say, http://example.com/)
2. Open DevTools panel (ctrl + shift + i)
3. Switch to a different Tab within the same Window
4. Check CPU usage in Chrome Task Manager (shift + esc)

What is the expected behavior?
CPU usage must not be 100%.

What went wrong?
Even though nothing is active in the devtools panel, cpu the browser is consuming full cpu time on all cores. this slows down the machine and also heats it up

Did this work before? N/A 

Chrome version: 59.0.3071.104  Channel: stable
OS Version: 
Flash Version: 

when recreating the bug, key things to remember:

1. keeping the Tab (with the DevTools panel open) "in focus" DOES NOT cause the issue.

2. keeping the Tab (with the DevTools panel open) "in focus" and opening a new Window DOES NOT cause the issue.

3. keeping the Tab (with the DevTools panel open) "out of focus" DOES cause the issue.

4. keeping the Tab (with the DevTools panel open) "out of focus" and working in another Window DOES cause the issue.

In summary, to create the bug, simply open DevTools in a Tab and navigate to a different tab in the same window.

Also,

1. attaching the DevTools to position "left", "right" and "bottom" DOES NOT affect the bug - it occurs as described.

2. detaching the DevTools panel (into a separate window?) prevents the bug.