UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. On angular 4.0 page that is rendered from a complex view/component specifically with mulitiple ngFor, ngIf, and nested components.  This doesn't effect all views. 
2. On windows 10 open the performance monitor in task manager tools, also make sure that chrome dev tools is open.  Make sure clear cache in dev mode is checked in settings.
3. refresh the page and notice that the system memory continues to increase after each page refresh. This will continue until the tab crashes (In the case i saw this occured after about 5 or 6 page refreshes).  If chrome devtools is not open this does not happen.

What is the expected behavior?
Chrome devtools should not retain significantly more memory if devtools is open compared to when it is not open.

What went wrong?
Chrome devtools does not clean up its memory in all cases very well in angular 4.0 with devtools open.

Did this work before? N/A 

Chrome version: 57.0.2987.133  Channel: n/a
OS Version: 10.0
Flash Version: