32669 - Mozilla used all the system resources, and Windows have gone.

Status: RESOLVED DUPLICATE of bug 145425

(SeaMonkey :: General, defect, P3)

Description

[YONEMURA Kaoru]

While I was trying to read very large (about 3MB) document with very high 
(about 100KB/s) rate, Mozilla used out all of system resources and user 
resources (I've checked it with resource-meter, which is distributed with 
Win98), and Windows have gone with.

buildID:2000032011

Comment 1

[Christine Begle]

[e-mail]: would you give us a URL that demonstrates this problem?

thanks

Comment 2

[YONEMURA Kaoru]

Yes, this is that:
http://www.hobbyj.co.jp/magic/freetalk/maillist.html

but the file is dynamic, so this error may not occur when you visit.

Comment 3

[Asa Dotzler [:asa]]

cbegle, this does indeed chew up all my resources.  After about 45 seconds I'm
at 99% CPU usage and when I hit the stop button mozilla locks up. I tried the
same page in IE4 and it pegged CPU even faster.  What's next in diagnosing this
issue?

Comment 4

[Christine Begle]

sounds like we need some profiling help to figure out what's going on here.

Comment 5

[Eugene Savitsky]

WFM with 2000080208 on WinMe, but I have only 64000 ISDN connection. %CPU was at 
3-6%.

BTW. Actually I'm continuing to load this page at this moment...

Comment 6

[Park Sang Hyun]

A blank page takes about 1% of system, GDI resource and usage increases to 5~8%
resources for ordinary pages. and it takes up to 15~25% resources with many
images or frames.
Some of them aren't returned when the window is closed. (Maybe 1~2$ of resource
are gone and not returned even in closing Mozilla.)

Comment 7

[Park Sang Hyun]

It looks almost solved in near-0.9 build.
I could open over 20 windows of ordinary homepage until resources drain and when
closed resources are returned well. After quitting Mozilla no resources are gone.

(BTW, I dunno what would happen when Moz is crashed or Java VM is loaded.)

Comment 8

[Park Sang Hyun]

Some pages use too much system resources.
For example, Java 2 API Specification page uses over 30%, Mozillazine uses over 15%.
I'm also afraid that the usage of resources is increasing recently.

Comment 9

[Oliver Six]

Attachment: Problem trace/test case?

Comment 10

[chris hofmann]

test url is no longer around.   do we still have the problem?

Comment 11

[Asa Dotzler [:asa]]

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

Comment 12

[YONEMURA Kaoru]

Moz doesn't kill Windows now, but it still uses all resources when opening
*HUGE* html file.

Comment 13

[Cees T.]

Sounds like http://bugzilla.mozilla.org/show_bug.cgi?id=148338 and
http://bugzilla.mozilla.org/show_bug.cgi?id=145425

Comment 14

[Grey Hodge (jX)]

A good way to test is to try to moderate any story on Slashdot with at least 100
comments. When you gt to the 300+ comment range, Windows tells you you're low on
resources, and you should stop doing whatever you're doing before you poke out
someoen's eye. Any page with lots and lots of widgets should do it. Moderator
views on /. do it nicely.

Comment 15

[Grey Hodge (jX)]

Attachment: Testcase. 263,977 bytes in size, but it's all text

This is a testcase for this bug. It's 260k in size, but it's all text and so
it's highlt compressable. PKZip takes it to under 2k in size, ,so even a modem
user will be able to pull this down in 15 seconds or so (assuming you use
compression, which 99% of you should be by default).

Load this page, and watch you'r win32 GDI/User resources go right down the
drain. Unload the page to magically make them reappear. I don't think this bug
is going to be too fixable unless we change the way to manage this type of
thing. To be fair,  IE does the exact same thing. Same page in IE causes all
sorts of malfunctions. We at least behave better in these cases.

Comment 16

[Jason Green]

Confirmed that this is still a problem as of Mozilla 1.2.1 on Windows 98 SE w/
all the latest patches.  I will check Monday if it affects Windows 2k.  I'm
running an Athlon 1600+ w/ 256 MB RAM, and it makes Mozilla nearly freeze.  

IE 6 SP1 w/ all the latest patches has a tough time with it, too.  It doesn't
freeze, but the drop-downs get lost/distorted, and right-click on the taskbar
doesn't work.

So, this may be a Windows bug, but there's got to be a way around it..

Comment 17

[Asa Dotzler [:asa]]

greenhja6, please don't use flags if you don't know how. To nominate a bug for
blocking 1.3a use the ? flag. Only drivers can set the + flag meaning that they
consider it serious enough to hold the release for.

Comment 18

[Dave Garland]

*** Bug 200619 has been marked as a duplicate of this bug. ***

Comment 19

[WD]

*** Bug 202966 has been marked as a duplicate of this bug. ***

Comment 20

[Alan Arndt]

I still have this problem with 1.4b and even more so with Firebird 0.6.  I had
been using Phoenix mostly and the past few months nightly builds seemed to be
even worse.  I use WinME and it frequently runs out of resources with multiple
tabs (6-12) open.  Closing all the tabs only releases part of the resources. 
Closing the browser entirely releases another large chunk, but I don't think all
of the resources are returned, only a reboot seems to solve it.

Note that this is a problwm with both the "System resources" and "GDI resources".

Comment 21

[Jim Booth]

I agree with Alan Arndt's comment #20 completely.   Using Mozilla 1.4b build
2003051408 on Windows ME.  

Mozilla can take me from over 70% available System resources and over 80% GDI
resources down to ZERO with about 10-12 tabs (often in 2 or more windows) open.  
None of the pages are particularly large.  

I never get back the last 8-10% of each after closing Mozilla.  Have to reboot
at least twice a day to get through the day, where I never had it this severe
before Late April 2003. 

This seems to have gotten MUCH worse in the last 3 weeks or so.  (Probably
should be a new bug, but I'm going to add the REGRESSION keyword to this one for
now.)

Also requesting BLOCKING 1.4 status.  This is really severe on my machine.

Comment 22

[Jim Booth]

Just found Bug 204374 which is probably a better match for my complaint about
recent worsening behavior.  I'll transfer the Regression keyword and 1.4 block
request to that one.  

Comment 23

[Jim Dunn]

Can someone on Win98 download the GDI usage tool that is attached on bug 199443
and run this against the "Testcase. 263,977 bytes in size, but it's all text"
(attachment 101144 [details]) and then tell me which resource(s) we are using up?

My win98 resource meter (after loading this test) has 
System resources: 20% free
User resources: 20%
GDI resources 74% free
however when I run in win2k, my GDI objects jump from 460 (before loading
to over 1100).  So I am trying to figure out which system resource we
are gobbling up.

btw comment #20 & comment #21 both reflect (I believe) the problem addressed
in bug 205893 (which I have a potential fix for)

Comment 24

[Johan Buret]

Using: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624

Config :  Athlon 1700+
          112 MB Ram
          Graphic Chipset on Motherboard

I've got on my desktop Mozilla with two tabs and the resource meter:
 Before loading: System 79% User 79% GDI 84 %   
 After loading(almost 1min): S 27% U 27% G 83%
 After reload(15 s): same results
 After closing the offending tab : S 79% U 79% GDI 83%

Comment 25

[Jim Dunn]

Thanks Johan, but I thought the win98 usage tool also reported
which GDI objects are being used (BRUSHES, REGIONS, BITMAPS)...
Without knowing which resource is being used up, not sure even
where to start (I don't have debugging capabilities on my win98 
machine).

Comment 26

[Johan Buret]

Attachment: Full report for GDI resources usage - tiny and safe :-)

Comment 27

[Bernd Wolff]

Hello, this looks like the problem I am experiencing with 1.4 and 1.5;
the first symptom on my Win98 was that the Asus Probe tool popped up error
messages like "Canvas does not allow drawing". Later fonts will be messed up
system-wide and windows improperly redrawn.

What I found when I started the Process Explorer from Sysinternals was that
with only a single download progress window open, Mozilla had still 20 open
threads - maybe they hog the resources?

Comment 28

[Christopher Wanko]

could someone update severity to "trivial", since it's clear "critical" is a joke?

Comment 29

[William A. McLaughlin]

Christopher, veto that.
a) For most users (very probably not anyone here OTH) this is a showstopper. 
Non-techie users are not going to know, nor should they be required to know, how
to get out of what appears to be a locked system, heretofor unseen error
messages, and/or all of their icons turning completely white (etc. - add your
own GDI resources low/exhausted symptom).

b) This is a longstanding problem, and this is far from the only bug which has
been opened here suggestive of GDI resource exhaustion.

c) From a technical point of view, this may seem like a minor issue.  OTOH,
someone in charge of deploying Moz over Internet Exploder is going to think
twice about doing so.  Consider, please, how many help desk calls this will
generate.

My two cents ...

Bill

Comment 30

[William A. McLaughlin]

Christopher, veto that.
a) For most users (very probably not anyone here OTH) this is a showstopper. 
Non-techie users are not going to know, nor should they be required to know, how
to get out of what appears to be a locked system, heretofor unseen error
messages, and/or all of their icons turning completely white (etc. - add your
own GDI resources low/exhausted symptom).

b) This is a longstanding problem, and this is far from the only bug which has
been opened here suggestive of GDI resource exhaustion.

c) From a technical point of view, this may seem like a minor issue.  OTOH,
someone in charge of deploying Moz over Internet Exploder is going to think
twice about doing so.  Consider, please, how many help desk calls this will
generate.

My two cents ...

Bill

Comment 31

[firemotion+mozilla]

*** Bug 193556 has been marked as a duplicate of this bug. ***

Comment 32

[William A. McLaughlin]

Status update:

Congratulations!

This situation was *vastly* improved upon in 1.5, and bug seems to be pretty
much squished in 1.6 - since moving to 1.6 I've had yet to see an occurence.

Bill Mclaughlin

Comment 33

[Wayne Mery (:wsmwk)]

WFM  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a3pre) Gecko/20070216 SeaMonkey/1.5a

Comment 34

[Wayne Mery (:wsmwk)]

benoit, do you see this problem on win9x in any reaonsable usage time period?

Comment 35

[Benoît]

I can't say I've ever had problems concerning resource usage by opening a lot of tabs and/or using SeaMonkey for many hours.

I loaded the testcase. SeaMonkey did not become sluggish, did not lock up, and did not crash. Viewing resources from an Explorer window's Info dialog, I see that I have 46% available. I press Back. Still 46%. I close the tab. 90% available.

At this point I had Google in a tab, my inbox and one e-mail open (in Mail & Newsgroups windows).

This is on a system with 160 MB of RAM using default resource settings. I hope this helps. If there is still a problem, it's not as severe anymore as this bug makes it out to be.

Comment 36

[OstGote!]

Resolving this old report as dupe of bug 145425 instead of WFM. If you can provide reproducable steps to reproduce this problem with current trunk builds feel free to reopen it.

Comment 37

[Benoît]

And how exactly do you want people on Win9x to reproduce with trunk builds when they don't run on Win9x?