Closed Bug 734857 Opened 10 years ago Closed 10 years ago
.0a1 memory spike in test Tab View _Open New Tab
Follow up on bug #728871 comment #9: The values increased with almost 10% since March 1 on: - Win NT 5.1.2600 x86: 280->315MB(max explicit memory), 449->481MB(max resident memory) Notes: 1. The increase affected Ubuntu 10.10 x86_64 and Mac 10.6.8 x86_64 as well: - Linux Ububtu 10.10 x86_64: 446->490MB(max explicit memory), 340->360MB(max resident memory) - Mac OSX 10.6.8 x86_64: 650->710MB(max explicit memory), 840->900MB(max resident memory) But on these platforms the numbers decreased since March 9 (to values similar to the ones before bug 728871) 2. The leak is caught by the open new tab tests: Feb 29 report: http://mozmill-release.blargon7.com/#/endurance/report/55d601cc2aabfac28f59060a84f943d4 (Win NT 5.1.2600 x86) - testTabbedBrowsing_OpenNewTab -> Max explicit memory: 243MB/Max resident memory: 329MB - testTabView_OpenNewTab -> Max explicit memory: 271MB/Max resident memory: 437MB March 1 report: http://mozmill-release.blargon7.com/#/endurance/report/e438d6e3916b2b636037d7744503407d (Win NT 5.1.2600 x86) - testTabbedBrowsing_OpenNewTab -> Max explicit memory: 272MB/Max resident memory: 360MB - testTabView_OpenNewTab -> Max explicit memory: 312MB/Max resident memory: 479MB Charts: http://mozmill-release.blargon7.com/#/endurance/reports?branch=13.0&platform=All&from=2012-02-29&to=2012-03-01
Looking at the bigger picture, it seems like the spike actually happened on Feb 19th and has now dropped off since March 9th. Resolving WORKSFORME for now -- lets reopen if it resurges.
Status: NEW → RESOLVED
Closed: 10 years ago
OS: Windows XP → All
Hardware: x86 → All
Resolution: --- → WORKSFORME
Summary: Memory leak increase with about 10% in open new tabs tests (Win XP) → Firefox 13.0a1 memory spike in testTabView_OpenNewTab
You need to log in before you can comment on or make changes to this bug.