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

Steps to reproduce the problem:
1. Start chromium and open some web page with ajax. Google inbox as instance. 
2. Log out and log in as another user. 
3. Wait for 4 hours

What is the expected behavior?
Chromium normally works in background or suspends all it's jobs. 

What went wrong?
Page process will use 2Gb of RAM and continue to grow. If you switch to first user again, chromium will start eating 100% (1 core) CPU releasing memory.

Did this work before? N/A 

Chrome version: 59.0.3071.86  Channel: stable
OS Version: Debian 8.8
Flash Version: Shockwave Flash 25.0 r0