G
Graham-1
Guest
This example is a complete web page that demonstrates a slow leak in IE9.
IE9.0.5 leaks a few bytes every time that backgroundPosition is called.
sIEve and Drip show a steady increase in usage of memory but no increase in DOM objects.
Leave it open for 8 hours or so and the IE tab dies when IE runs out of memory.
Reloading the page or going to another page recovers memory - but can be delayed by tens of minutes by what appears to be memory clean-up.
CollectGarbage helps even out the stats but has no effect on the overall bug or steady increase in memory used.
Please help !
Thanks.
Graham
MCSD/ MCAD .Net, MCSE/ MCSA 2003, CompTIA Sec+
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<div style="margin: 0px auto; width: 100%; height: 100%;">
<div style="margin: 0px auto; width: 230px; color: white; font-size: 12px; font-variant: small-caps; float: left">
<div style='width: 350px; height: 56px; background-image: url("http://www.microsoft.com/global/oneMscomSettings/PublishingImages/HeaderImages/WindowsLogo.png");
background-color: black;' id="my_datecounter_1">
<div style="float: left; display: inline-block; background-color: white;">
<script type="text/javascript">
var progress = 0.0;
var timerDateId = window.setInterval(function(){
var temp = document.getElementById("my_datecounter_1");
progress = progress + 0.4;
if (progress > 600) {
progress = 0;
if (typeof(CollectGarbage) == "function") {
CollectGarbage(); / try and make watching stats easier and discount pseudo-leaks /
}
}
var bpos = "0px " + parseInt(progress) + "px";
temp.style.backgroundPosition = bpos;
},
10);
</script>
Continue reading...
IE9.0.5 leaks a few bytes every time that backgroundPosition is called.
sIEve and Drip show a steady increase in usage of memory but no increase in DOM objects.
Leave it open for 8 hours or so and the IE tab dies when IE runs out of memory.
Reloading the page or going to another page recovers memory - but can be delayed by tens of minutes by what appears to be memory clean-up.
CollectGarbage helps even out the stats but has no effect on the overall bug or steady increase in memory used.
Please help !
Thanks.
Graham
MCSD/ MCAD .Net, MCSE/ MCSA 2003, CompTIA Sec+
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<div style="margin: 0px auto; width: 100%; height: 100%;">
<div style="margin: 0px auto; width: 230px; color: white; font-size: 12px; font-variant: small-caps; float: left">
<div style='width: 350px; height: 56px; background-image: url("http://www.microsoft.com/global/oneMscomSettings/PublishingImages/HeaderImages/WindowsLogo.png");
background-color: black;' id="my_datecounter_1">
<div style="float: left; display: inline-block; background-color: white;">
<script type="text/javascript">
var progress = 0.0;
var timerDateId = window.setInterval(function(){
var temp = document.getElementById("my_datecounter_1");
progress = progress + 0.4;
if (progress > 600) {
progress = 0;
if (typeof(CollectGarbage) == "function") {
CollectGarbage(); / try and make watching stats easier and discount pseudo-leaks /
}
}
var bpos = "0px " + parseInt(progress) + "px";
temp.style.backgroundPosition = bpos;
},
10);
</script>
Continue reading...
