3 ms·
This looks like a fairly old leak in all WebKit browsers. There's a year+ old bug about it filed against Chromium, and I think there's one against WebKit proper
by kevingadd 16y ago
This looks like a fairly old leak in all WebKit browsers. There's a year+ old bug about it filed against Chromium, and I think there's one against WebKit proper as well: http://code.google.com/p/chromium/issues/detail?id=36142 http://code.google.com/p/chromium/issues/detail?id=36142
Frustratingly, the chromium and webkit devs seem to have been ignoring it. In my case, it made one of my products completely unusable on all webkit-based browsers... which includes Android, WebOS and iOS. Sigh.
- othermaciej 16y agoHere's the upstream WebKit bug which has some more analysis: https://bugs.webkit.org/show_bug.cgi?id=61006 https://bugs.webkit.org/show_bug.cgi?id=61006
- nitrogen 16y agoThe bug you link here (36142) is important because demonstrations there show that memory grows unbounded even without using no-store (one demonstration uses images from the local hard drive, from whence no cache control directives could possibly be obtained, and eats through ~1.3GB/min of RAM).