Live data from Hacker News

All modern web-browsers except IE9 are vulnerable to a huge memory leak

code.google.com

31–40 of 71 posts

Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak

#31

Now, let's see which of these browsers fix this issue the fastest. My bet is that Chrome will be the first.

It looks like the first was IE9 - see http://code.google.com/p/chromium/issues/detail?id=36142#c53 . Chrome doesn't fix the related bug for more than a year - http://code.google.com/p/chromium/issues/detail?id=36142 . Safari wins with more than two years - https://bugs.webkit.org/show_bug.cgi?id=23372 .

Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak

#35
post #14
post #3

Haha, the irony.

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.

IE9 also had this bug, but it has been fixed - see http://code.google.com/p/chromium/issues/detail?id=36142#c53

Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak

#36

From personal experience I'll chime in that IE9 crashes just frequently enough for memory leaks not be a huge issue.

Zing! There was an issue with pre PHP5.3 where circular references caused memory leaks. In code that could not be moved to 5.3, long running processes were written to auto-restart at a certain point.

Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak

#38

Earlier quoted context omitted.

No. He's replying from the future.

Firefox nightly builds are currently 6.0a1.

Ahh, thanks. Do nightly build version numbers roughly correspond to release versions? That is, are the features in FF6(n) the same as those that will be in FF6(f)?

Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak

#39

Earlier quoted context omitted.

Firefox nightly builds are currently 6.0a1.

Ahh, thanks. Do nightly build version numbers roughly correspond to release versions? That is, are the features in FF6(n) the same as those that will be in FF6(f)?

Yes, they correspond.

Currently FF Nightly is 6. That will become Aurora 6, then Beta 6, and then Firefox (final) 6. The features in all of those should be the same, except that we might fix some bugs along the way and/or disable some features if they are not stable enough after testing. No new code is landed on Aurora, Beta or final, except for those fixes and possible disablings.

Re: All modern web-browsers except IE9 are vulnerable to a huge memory leak

#40

If swap trashing makes a system unusable, why not get rid of the swap and let the program crash? Isn't that the preferred behavior?

swapping is a fundamental part of a multi-tasking o/s and unfortunately unless a program starts writing into memory addresses that have not been allocated to it the o/s would not be able to know if the program is crashing or not (segmentation faulting)...

to the o/s this bug would just look like a memory hungry program so it just keeps on allocating more memory... once all physical memory has been used up, the o/s has to swap out old data to disk and re-use addresses for this program that just doesn't stop asking for more memory... i.e the program doesn't know it's doing stupid shit and the o/s doesn't know it is hosting a stupid program..

it's kinda like a house party where everyone starts the night normal, then as the night goes on some idiot doesn't recognize their own limits and they keep drinking more and more and the host doesn't know what this guy is doing and before he knows it he has to clean up vomit in the morning...

hope this makes sense..

Post reply on HN