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

Steps to reproduce the problem:
1. Open http://jsfiddle.net/dandv/57fk1pzy/ in a new tab.
2. Wait a few seconds until you're sure the tab has become unresponsive (nothing will happen if you press F12 to invoke DevTools, or Shift+Esc to bring up the task manager)
3. Close the tab via Ctrl+W or by clicking its 'x' icon
4. Repeat from step 1 four times.

Now inspect the CPU utilization in the Chrome Task Manager and in the system's Process Monitor.

On my Ubuntu laptop I see all 4 cores at ~100% utilization.

What is the expected behavior?
Very low CPU utilization after the offending tab has been closed.

What went wrong?
Perhaps the while(true) look from the JSFiddle keeps running even after the tab was closed?

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: stable
OS Version: Ubuntu 16.04.1
Flash Version: Shockwave Flash 23.0 r0

Related: issue 630840
 

Deleted: CPU utilization leak 1.png 33.8 KB

	CPU utilization leak 1.png 33.8 KB View Download

Deleted: CPU utilization leak 2.png 69.2 KB

	CPU utilization leak 2.png 69.2 KB View Download