For years now, browser developers haven't been able to fix memory leak problems. For example, more than a year ago, this bug was reported for Chromium (
# 36142 ), but so far the situation has not shifted from the dead point. Similar reports
were submitted to Bugzilla a long time ago.
The next stage of this endless epic is a new example of very large memory leaks (
# 81517 for Chromium). It differs from # 36142, since leaks are recorded here without using a cache, but by the method of multiple loading of one image into RAM with the NO-STORE attribute.
Since the browser does not free up memory before closing the document, within a few minutes
a 22 KB JPEG image leads to the complete exhaustion of any amount of RAM and the browser collapse. Bug confirmed for Chromium 11.0.696.60, Safari 5 and Firefox 4.x. Vulnerability applies to all browsers on the engine WebKit.
The IE 7/8/9 family and Opera 11.10 passed the test successfully. It is interesting that in IE9 this bug was also present, but it was quickly
fixed .
')
It is said that Firefox 3.6 and Firefox 6.0a1 also pass the test. The remaining versions need to be checked. The test is located at
memleakbug.appspot.com .