What can cause a shared (non-js heap) memory leak in Google Chrome?

Question

JavaScript

There is a small application inside the browser: a dashboard with d3.js charts, under the backbone/underscore hood. The data on the dashboard and graphs are regularly updated by the standard backbone mechanisms (updating the model with cascading view updating). At the same time, the set of backbone objects and the configuration of event subscriptions do not change.
With a long stay in the browser (well, or with a fairly frequent data update, which is essentially the same thing), we have a memory leak. And:
1. there is a leak only in chrome, ff works fine.
2. all monitoring tools (task manager, developer tools/timeline) show that the javascript heap size is stable (stably filled with objects and cleared by GC)
3. at the same time, the task manager shows a relatively stable increase in the memory size of the process that performs the bookmark with the application. (relatively stable - with local rebounds, but growth nonetheless). both the memory parameter and the private memory parameter grow.
4. The sizes of caches (statics, graphics) do not change according to the indications of the task manager.
Accordingly, the questions are:
1. Do I understand the problem correctly? Indeed, can we assume that this leak is not in a js application, but somehow it turns out differently?
2. In general, what data gets into private memory? What determines the size of this section?
3. How to deal with it? Where to dig?

Answer 1

Everything works fine: https://jsfiddle.net/alexey_m_ukolov/e4vq78ch/ (it's 23:20 for me now).
You do not confuse 10 hours and 22 hours?

Answer 2

I have the latest version of Chrome strange somehow works. Sometimes some add-ons (mostly add-ons that are frequently updated: weather and mail buttons) fall off with a bang or consume a lot of memory / cpu.
This was noticed a couple of times under the Linux build of chrome. Restarting seems to help.
Maybe it's some kind of Google bug?

Answer 3

Chrome version is 37.0.x, I'm currently trying to upgrade to the current version.
Of the extensions, I only had hangout enabled (as it turned out - the browser is used for testing and does not require extensions). I turned off the extensions, now I'm checking if the behavior changes.
But the problem is that clients caught this error. I highly doubt they had a set of extensions enabled that correlated with mine.