Closed Bug 296188 Opened 19 years ago Closed 19 years ago

used memory increases if the refresh button get activated different times

Categories

(Firefox :: File Handling, defect)

Product:
Firefox
Component:
File Handling
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: julika.burger, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Also Operating System XP, Firefox Version 1.0.2

I wrote the following html file and every time I reload this file the used
ram(memory)increase. I also integrate the mozilla as a active x control in my
programm and therefore I also use the refresh process different times so its
important for me to fix this problem:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html>
<head>

<title>AdServer</title>       
</head>
<body>
  <div id="globalcontentleft" class="cbar">
        <div id="lea_468x60" align="center"></div>
  </div> 

  <script language="javascript1.1" type="text/javascript">
    var refurl="http://www.lycos.de/kommunizieren/index.html";
    var other = "ee=0";	
    lea_getter(refurl,other,"de");

function lea_getter(refurl,other,cc) {
  var adsrv, i;

  switch(cc)
  {
    case "dk": 
      adsrv="http://ads2.jubii.dk/ats/";
      break;
    case "no": 
      adsrv="http://fe.lea.nettavisen.no/ats/";
      break;
    case "se": 
      adsrv="http://fe.lea.spray.se/ats/";
      break;
    case "uk": 
      adsrv="http://fe.lea.lycos.co.uk/ats/";
      break;
    case "test":
      adsrv="http://devadclient01.st1.spray.net/ats/";
      break;
    case "stage":
      adsrv="http://ats.vip.spray.net/testads/";
      break;
    case "fail":
      adsrv="http://adclient81.st1.spray.net/testads/";
      break;
    default:
      adsrv="http://fe.lea.lycos."+cc+"/ats/";
  }

  now = new Date();
  var ts = now.getTime();
  var alldiv=document.body.getElementsByTagName('div');
  var adstring=adsrv+'getad.php?adinfo=';
  
  for (i=0;i<alldiv.length;i++) { if (alldiv[i].id.indexOf('lea_') == 0) {
adstring += alldiv[i].id + "|"; } }
  document.write('<scr'+'ipt
src="'+adstring+other+'|'+escape(refurl)+'|'+ts+'"></scr'+'ipt>');
  
}
  </script>
</body>


Reproducible: Always

Steps to Reproduce:
1. Open the file in the mozilla
2. also start the taskmanager and have a look at the procss "firefox.exe",
memory use
3. Now activate the reload button different times
=> the memory use increase
Severity: normal → major
Summary: used memory increases if the refresh button get activated different times → used memory increases if the refresh button get activated different times
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.