UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Open various webpages containing twitter subframes
2. Check the Chrome task manager
3. You may see CPU usage stay stuck to 100%

What is the expected behavior?

What went wrong?
As an end user using Chrome heavily, I've opened a bunch of tabs, the CPU usage can be reasonable in most cases, that is until the process that contains series of "https://twitter.com/" subframes is launched and maxes out CPU Thread(s). I can temporarily remedy this by killing the process, but they may reappear over time or once I restart the browser.

I'm not sure whether this is a result of a website programming decision or an element in a subframe process that triggers Chrome to start an infinite loop inside of it, but either way I don't think Chrome should be allowing background subframes to indefinitely consume 100% CPU.

Did this work before? N/A 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: 10.0
Flash Version:
 

Deleted: twittersubframe maxed cpu.png 23.7 KB

	twittersubframe maxed cpu.png 23.7 KB View Download