javascript - Chrome tab memory keeps growing, heap size stays the same -


i'm working team on single page application quite few timers, , 10 rest api calls per second. we've used chrome memory profiling tools locate of our memory leaks--at point heap size stays same (i.e. in between garbage collections). however, we're noticing longer application runs, more memory chrome tab uses. after few hours, we've seen tab memory grow 350mb, while heap size remains @ 6mb. if run overnight, tab consumes on 500mb , becomes unusable morning.

we need application run long periods of time (we're hoping restart once week), problem.

here's screenshot of heap timeline on course of hour. @ end, tab's private memory size 350mb, while heap's size remained @ around 5.4mb.

enter image description here

we've seen in chrome 40 , chrome 38, on windows 7. have caching disabled, , running application in incognito mode.

any idea why tab memory size grow point chrome unusable, while js heap usage remains small?

edit: ran app couple days , tab memory size 800mb, heap size still same.

edit (6/9/15): i'm not sure if documented anywhere, seems chrome changes amount of memory allocate tab, based on amount of free memory on system. so, if have lot of free memory, tabs use lot of memory, , if don't have much, won't use much. doesn't seem proportional heap size, it's stuff chrome keeps around make faster. theory, based on monitoring chrome memory usage :)


Popular posts from this blog