Plugging Internet Explorer's Leaks 480
jgwebber writes "If you're developing DHTML web apps, you probably already know first-hand that Internet Explorer has horrendous memory leak issues. You can't not run on IE, so you've got to find a way to plug those leaks. So I've created a tool to help you find them. So until Microsoft decides to fix its browser architecture (ha!), at least we can keep it from blowing huge amounts of memory."
Not Microsoft's Fault (Score:4, Funny)
Korean outsourcing
Making sites not run on IE (Score:2, Funny)
<?
if (preg_match("/MSIE/i", $_SERVER["HTTP_USER_AGENT"])) {
header("Location: http://www.mozilla.org/products/firefox/");
exit();
};
?>
<html>
<head>
<title>This site will not display in Internet Explorer</title>
.
.
.
</head>
<body>
.
.
</body>
</html>
Re:Quick and dirty fix (Score:5, Funny)
Please, tell us more about the fascinating workings of computers you seem to know so much about.
Re:Quick and dirty fix (Score:0, Funny)
And your new OS do not have Firefox ?
Re:Quick and dirty fix (Score:2, Funny)
I think you made a simple typo in this sentence. It should read Thus 16 megabytes = 1283918464548864 bytes.
Re:Quick and dirty fix (Score:1, Funny)
Re:NOOB... (Score:3, Funny)
Re:NOOB... (Score:1, Funny)
Usually operating systems will free memory allocated to an application when it exists. There are probably ways to confuse every operating system and prevent this, though.
In any case, it's generally considered bad form to ever rely on the OS to free your memory for you (at least in languages where you have to manage the memory), and leaks that accumulate in your main loop are obviously a big problem.
Where does the memory leak to?
If the leaked memory does not share a page with often-used memory in a separate allocation, it eventually gets push out to the pagefile. Eventually (could take a LONG time) the application will exhaust its address space and die, but it won't really affect other applications too much. (there's less virtual memory available, but you're probably in trouble anyway if you're that close to the limit)
If the leaked memory DOES share a page with other goodies, it'll eat up part of your physical memory and ultimately lead to more heavy swapping, slowing down the machine.
Most likely you'll end up with some combination of these two. Smaller leaks will tend toward using physical memory, larger ones (relative to the machine's page size) toward pagefile.
Re:NOOB... (Score:3, Funny)