The issue of memory leaks in Firefox 3 has almost disappeared
CNET's Adrian Kingsley-Hughes, Adrian Kingsley, decided to check if the first beta version of Firefox 3.0 lost the disease of previous browser versions. To do this, he conducted a series of tests for the browsers Firefox 3.0 beta and Firefox 2.0.0.9.
Testing was carried out on a computer running Windows Vista Home Edition with 2GB of RAM, and never before on this machine did Firestone stand. Representatives of two generations of Mozilla browser with standard settings were installed on the computer. With the help of both browsers, Kingsley-Hughes visited the same sites.
Thus three scenarios were reproduced:
That's what came out of it.
')
Firefox 2.0.0.9
Firefox 3.0 b 1
Adrian Kingsley-Hughes repeated the test with a five-minute wait and 12 loaded pages in Internet Explorer - “Donkey” during this time “grabbed” 89,756Kb of RAM. That is, his appetites are more than Firefox 3.0 beta 1, but still more modest than Firefox 2.0.0.9.
It's funny that in the first tests it seemed that Firefox 3.0 beta 1 was more demanding on resources than 2.0.0.9, but when passing the 12-page test it became noticeable that over time the appetites of Firefox 2 started to increase - it is possible that continuing testing after five Firefox 2 minutes would “eat” even more memory. With the beta version of Firefox 3.0, this, fortunately, did not happen. In general, the problem of memory leaks can be considered practically solved.
Testing was carried out on a computer running Windows Vista Home Edition with 2GB of RAM, and never before on this machine did Firestone stand. Representatives of two generations of Mozilla browser with standard settings were installed on the computer. With the help of both browsers, Kingsley-Hughes visited the same sites.
Thus three scenarios were reproduced:
- Loading in the browser of five pages;
- Loading one page and weaning from a computer for 10 minutes;
- Download 12 pages and separate from the computer for 5 minutes.
That's what came out of it.
')
Firefox 2.0.0.9
- After downloading five pages, Firefox ate 35.640Kb;
- Ten minutes after loading one page, Ognelis selected 47.852Kb of RAM;
- Five minutes after downloading a dozen pages, the most popular alternative browser "ate" 103,180Kb.
Firefox 3.0 b 1
- After downloading the five sites Fox Fox raked for themselves 38,644Kb;
- Ten minutes after loading one page, Firefox grabbed 63.764KB of RAM;
- After five minutes of inactivity with 12 downloaded pages, Firefox ate 62,312KB.
Adrian Kingsley-Hughes repeated the test with a five-minute wait and 12 loaded pages in Internet Explorer - “Donkey” during this time “grabbed” 89,756Kb of RAM. That is, his appetites are more than Firefox 3.0 beta 1, but still more modest than Firefox 2.0.0.9.
It's funny that in the first tests it seemed that Firefox 3.0 beta 1 was more demanding on resources than 2.0.0.9, but when passing the 12-page test it became noticeable that over time the appetites of Firefox 2 started to increase - it is possible that continuing testing after five Firefox 2 minutes would “eat” even more memory. With the beta version of Firefox 3.0, this, fortunately, did not happen. In general, the problem of memory leaks can be considered practically solved.
Source: https://habr.com/ru/post/16567/
All Articles