From personal experience I'll chime in that IE9 crashes just frequently enough for memory leaks not be a huge issue.
All modern web-browsers except IE9 are vulnerable to a huge memory leak
21–30 of 71 posts
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#22Earlier quoted context omitted.
I dont think this is very ironic. IE9 is native to MSWIN and is written by the people who have the deepest knowledge of the operating system. They probably found this issue and fixed it before it was exposed to the other teams like Goog and Mozilla.
I don't see how the deepest knowledge of Microsoft Windows would help them fight website memory usage issues. Those things are entirely unrelated. However the reported bug is non-trivial, therefore it would be very strange if it would manifest itself identically on different non-related browsers. They might all leak, but I doubt they all leak 1M for 22kb file.
>"non-related browsers"
Chrome and Safari both use webkit. Of course that doesn't explain Firefox.
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#23Can't reproduce in Firefox 6 neither.
Firefox 6? Do you mean 3.6?
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#24Earlier quoted context omitted.
I dont think this is very ironic. IE9 is native to MSWIN and is written by the people who have the deepest knowledge of the operating system. They probably found this issue and fixed it before it was exposed to the other teams like Goog and Mozilla.
I don't see how the deepest knowledge of Microsoft Windows would help them fight website memory usage issues. Those things are entirely unrelated. However the reported bug is non-trivial, therefore it would be very strange if it would manifest itself identically on different non-related browsers. They might all leak, but I doubt they all leak 1M for 22kb file.
1 MB works out at 32 bits per pixel for a 512x512 image. The JPEG is probably not rasterized until it's viewed, which would explain why only an amount corresponding to the compressed image is leaked when the tab is hidden.
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#25Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#26[deleted]
I'm not sure where you got that from, but just so everybody's clear, this leak isn't in Flash — it's somewhere in the browsers' image loading code. Odd that an identical bug would be present in both Chrome and Firefox.
Not that odd. It sounds like there is no duplicate-checking going on. It's something that seems like it could be easy to miss.
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#27Can't reproduce in Firefox 6 neither.
Firefox 6? Do you mean 3.6?
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#28How does the reporter know this is a leak? High memory consumption is not a "memory leak".
The RFC says the data can be retained in history buffers as part of normal operation and as far as I can tell that's what is happening here.
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#29How does the reporter know this is a leak? High memory consumption is not a "memory leak". The RFC says the data can be retained in history buffers as part of normal operation and as far as I can tell that's what is happening here.
It is OK to have in-memory cache for certain resources. It isn't OK when this cache doesn't shrink under memory pressure. This usually leads to swap trashing after the cache becomes bigger than the available physical RAM on the system. Swap trashing makes the system unusable in most cases. See the comment #6 http://code.google.com/p/chromium/issues/detail?id=81517#c6 .
Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak
#30How does the reporter know this is a leak? High memory consumption is not a "memory leak". The RFC says the data can be retained in history buffers as part of normal operation and as far as I can tell that's what is happening here.
It is OK to have in-memory cache for certain resources. It isn't OK when this cache doesn't shrink under memory pressure. This usually leads to swap trashing after the cache becomes bigger than the available physical RAM on the system. Swap trashing makes the system unusable in most cases. See the comment #6 http://code.google.com/p/chromium/issues/detail?id=81517#c6 .
Ah, that was added after my comment. Nevertheless, there is no evidence this is a memory leak.