Closed Bug 265139 Opened 20 years ago Closed 20 years ago

firefox memory usage jumps from 2.5% to 18.5% (of 1gb) from javascript alert

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bugzilla.mozilla.org, Assigned: bugzilla)

References

()

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041014 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041014 Firefox/0.10.1

This seems to happen on firefox for Linux, cannot reproduce currently on win32.

Reproducible: Sometimes
Steps to Reproduce:
1. run firefox to http://www.google.com
2. view memory usage in top (2.5%)
3. change URL to http://www.velocity.net/~dale/firefox-test-js-alert/
4. view memory usage in top (18.5%)
Actual Results:  
firefox and rest of PC slows down considerbly (swapping)

Expected Results:  
behaved as Mozilla does - no memory spike.

default theme,
Arch Linux Current using firefox 0.10.1
Summary: firefox memory usage jumps from 2.5% to 18.5% (of 1gb) when viewing this page → firefox memory usage jumps from 2.5% to 18.5% (of 1gb) from javascript alert
I've also had this happen without the attached javascript being called.  It
seems that I can observe a 20% (~200Mb) memory usage by just using the browser
normally for a couple hours or so.
this hasn't seemed to happen for me since firefox 1.0, have there been any
changes that would affect this?
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041014
Firefox/0.10.1
> Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041014
Firefox/0.10.1
> 
> This seems to happen on firefox for Linux, cannot reproduce currently on win32.
> 
> Reproducible: Sometimes
> Steps to Reproduce:
> 1. run firefox to http://www.google.com
> 2. view memory usage in top (2.5%)
> 3. change URL to http://www.velocity.net/~dale/firefox-test-js-alert/
> 4. view memory usage in top (18.5%)
> Actual Results:  
> firefox and rest of PC slows down considerbly (swapping)
> 
> Expected Results:  
> behaved as Mozilla does - no memory spike.

FF and mozilla are not necessarily comparable in memory usage, given that many
memory improvements have been made to moz and (until now) not present in FF. 
You'd need to state what release+date of each you were comparing.  You say you
have 1gb memory, so I wouldn't think you should be hitting a wall, but I'm not a
linuxite.  You should provide more details about your test case like what other
apps are running and memory counts and amounts (not %).

But it may be a mute point ... FF nightly recently had the latest and greatest
moz fixes integrated from the trunk (moz version 1.8a6) including memory and
performance improvements.  Suggest you test the nightly (available top left at
mozillazine.org) and report back positive or negative relative to whether it
helps your example problem.  

Reported memory bugs are a dime a dozen (approx 300 new and unconfirmed bugs, 45
of which mention java).  If you still have a problem then you'll need to provide
more info, and should do some research into other bugs to see if you're a
duplicate
https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=memory&product=Core&product=Firefox&product=Mozilla+Application+Suite&long_desc_type=substring&long_desc=java&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

Leaving unconfirmed pending reporter feedback.
The bug I mention here is gone in firefox 1.0.

It's fine to close by me.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050322
Firefox/1.0+

Unable to reproduce using the testcase provided.  Per the reporter saying the
bug is no longer present, and being unable to reproduce, I am resolving this WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: