Firefox wastes too much GDI heap resources while browsing during several hours




14 years ago
13 years ago


(Reporter: tomman, Assigned: bugzilla)


1.0 Branch
Windows ME

Firefox Tracking Flags

(Not tracked)




14 years ago
I am one of that users that surt the web during too many hours, and i've
noticed, after opening and closing lots of tabs, and especially, new windows,
Firefox eats too much GDI resources, and even it does not free an ammout of it.
For example: browse during 3-4 hours, open some windows, and you will get 40-45%
of GDI heap (or even less, <30%) free, EVEN WITHOUT RUNNING ANOTHER
APPLICATIONS!. Close Firefox, and GDI heap will return only to 50-55% (normal
free GDI on my system is ~70-75%). And there are not only GDI resources waste,
some times, when opening pages on tabs or new windows after some hours results
in slowdowns, and Firefox locks by 2-3 seconds, with 95% of CPU usage.

I see a BIG memory leak, especially with the GDI heap

Comment 1

14 years ago
I have the same problem running:
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 with
512Mb RAM on Win98Se (IE6 updates installed)

I can run my resources down by simply refreshing a webpage with a lot of flash
content such as macromedia's page or some game pages.  Once the resources drop
to less than 50% the system gets unstable and FF either crashes or if I manage
to close it down and restart it, the resrouces do not come back up to 80%+,
often just 55%.  A reboot is needed to clear it up. Somestimes the system won't
reboot and crashes then.  
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.