Closed
Bug 804787
Opened 13 years ago
Closed 12 years ago
firefox memory usage explodes on www.morethanamap.com/demos/
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: thierry.vignaud, Unassigned)
Details
(Whiteboard: [MemShrink:P2][js:t])
Attachments
(1 file)
|
382.88 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:19.0) Gecko/19.0 Firefox/19.0
Build ID: 20121023030553
Steps to reproduce:
I visited http://www.morethanamap.com/
I then clicked on the "view demo" link when "Data Visualization" is displayed.
I then selected "earthquakes"
(http://www.morethanamap.com/demos/visualization/earthquakes)
Then "population" (http://www.morethanamap.com/demos/visualization/population) once it was completed.
As the population demo goes on, firefox memory usage went from ~300Mo up to 1.8Go at which time I had to desperately kill some the firefox process in order to maintain my system usable.
This with firefox nightly, on Linux x86_64 (Mageia Cauldron) with mesa-9.0 on a Radeon X1650 PRO video card using the radeon free driver.
Actual results:
Firefox (nightly) eats all memory, making the system slow (swap storm until I killed firefox)
Expected results:
Firefox should have maintain using some reasonable amount of memory
Comment 1•13 years ago
|
||
Could you please copy the output of "about:memory?verbose" and paste it into an attachment to this bug?
Followed your steps with Ubuntu, I had a maximum of 500 MB while the population demo was running, but it quickly went down to normal values (100 something) after 2-3 seconds.
Component: Untriaged → General
Updated•13 years ago
|
Flags: needinfo?(thierry.vignaud)
Comment 2•13 years ago
|
||
This sounds like it could be a driver bug. Can you re-test with
layers.acceleration.disabled
set to true in about:config? (At least, I think that's the right pref.)
Comment 3•13 years ago
|
||
Yeah, this really smells like hwaccel problems.
Whiteboard: [MemShrink] → [MemShrink:P2]
Updated•13 years ago
|
Component: General → Graphics
Product: Firefox → Core
| Reporter | ||
Comment 4•13 years ago
|
||
That doesn't change anything.
For the record, I'm using noscripts, adblock plus, firebug, greasemonkey, session manager
as well as two dictionnary extensions:
- Dictionnaire francais
- Difazier an drouizig
Flags: needinfo?(thierry.vignaud)
| Reporter | ||
Comment 5•13 years ago
|
||
Comment 6•13 years ago
|
||
Specifically, there's over a gig of elements, which seems unusual. Perhaps the fault is JS and not graphics...
Assignee: nobody → general
Component: Graphics → JavaScript Engine
Comment 7•13 years ago
|
||
Would you mind trying in safe mode? Sometimes add-ons do dumb things, and this doesn't sound like the type of add-on leak that we've prevented wholesale (bug 695480).
http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Flags: needinfo?(thierry.vignaud)
Comment 8•13 years ago
|
||
I also couldn't reproduce on 64-bit Ubuntu. The fact that it's JS array elements makes me now think that it's probably due to an add-on. Restarting in safe mode (see comment 7) temporarily disables add-ons, so if that fixes the problem we know it's an add-on. After that, it's a matter of selectively disabling add-ons and trying again to reproduce. My bet would be on a GreaseMonkey script causing the problem, but I could be wrong.
Updated•13 years ago
|
Whiteboard: [MemShrink:P2] → [MemShrink:P2][js:t]
Comment 9•12 years ago
|
||
This has been sitting for a long time, so I'm going to close it. Thierry, if you have time to answer our questions, please re-open this bug and we'd be happy to investigate further.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(thierry.vignaud)
Resolution: --- → INCOMPLETE
| Reporter | ||
Comment 10•12 years ago
|
||
Actually as of ff-22b1, the issue is fixed.
Component: JavaScript Engine → Graphics
Updated•9 years ago
|
Resolution: INCOMPLETE → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•