@Opcode...It doesn't do it by itself. It drives up the system memory, I suspect collecting links to freshly cached data and also maintaining cached data in memory too (maybe even after the page has been closed and even after the data is no longer in the disk cache). Open and close alot of pages over the period of time (have fun basically


) and use the PC hard (daily hard use), and the memory will climb. Security apps I suspect climb because they are finding more about Chrome's activity to monitor with a large number of tabs and that drives up other security apps like NVT ERP, etc. Comodo stays pretty stable, but so do most of these really.
Chrome actually doesn't use itself more than 5-6 GB. System memory, however, at that point will be up to 100% and all the page file will be used too. That brings the alert->out of virtual memory. Systen memory includes Windows uses too. BTW, svchost (Local System Network Restricted) climbs with Google too. It will get up to about 250K over this kind of a long boot and under these circumstances (again...on Windows 7).
I wouldn't call it a leak, because for me there is the question of whether the OS based memory control could or should be better in Windows 7. If it could be better, then maybe there could also be a way to make it easier for devs to optimize their apps with less work. This is the same tug of war that has been going on between MS and devs for I guess 20 years now. Not anything new. MS decides with regards to kernel optimization how things should be and devs write for whatever they decide...that simple. I can say that the combination of Windows 7 and Chrome running for 8 days with video streaming constantly and the PC running 24/7 will break system.
Can't say what would happen on W10 because I haven't tested to see if MS built any high end memory usage defense. BTW, this all goes back even to the late nineties where the get more memory argument took over. It's a fine thing to say, but I still believe a system (OS) should have upper end memory guards against system breakage. However, add more memory would certainly make the boot last alot longer...or at least I would think so. Running 16 GB, I suppose the single boot could go for 20-30 days. Running 32 GB, it might find 100% stability, just can't say.
I just don't think it would be wrong to consider that that some users will have 2 GB or 4 GB...that kind of thing.
You know
@Opcode, you could be 100% right though. There actually could be a leak in say uBlock or one of the other extensions I run. For sure, there can be those as I have seen here with, for example, the disk activity monitor widget for W7. That would directly store data in memory and never stop adding to the database. Talk about questionable. In the case of W7 and Chrome, this is why I wouldn't say it's a leak though. Still, now that I think about it, I wouldn't want to rule it out for sure. I mean, how often do systems get tested this way for an extension dev to realize an oversight etc...