290866 - system overload while loading this forum thread with huge post in there

Status: RESOLVED INVALID

(Core :: General, defect)

Description

[wroot]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Not sure if it's a bug. First time this happens with this forum and with Firefox
after 5 months using it (1.0.2 and 1.0.3). There is a huge post in this forum
thread (list of debian packages or something). And somehow i'm getting 100% CPU
load and almost not functional system (have to kill Firefox process) after
entering this thread. Always reproducable, on two PCs (win2000 and WinXP). The
more powerfull PC actually loads this thread after some time, but until that you
cant do anything with system (100% load). One more forum visitor have noticed
same behavior with Firefox and this thread. I think it affects only win32 version.

Reproducible: Always

Steps to Reproduce:
1.launch Firefox
2.go to
http://www.bite.lt/plius/bendravimas/klubai/2forum.showPosts/449703.461-=(1671833494

Actual Results:  
100% CPU load, almost not functioanl system

Expected Results:  
loading this thread normally without side effect

using some extensions: Tabbrowser Extensions, FlashGot, AdBlock, AutoCopy,
RightEncoding, Extended Statusbar, Html validator, DragToTab, Flat Bookmark
Editing, Sort Extension, Stop/Reload.

1. Athlon 550MHz, 192MB SDRAM, Acorp VIA chipset, win2000 SP3
2. Celeron 2.6GHz, 256MB DDR, WinXP SP2

Opera amd IE loads it normally

Comment 1

[Steve England [:stevee]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050418
Firefox/1.0+
I also see this.

Comment 2

[zug_treno]

Loading the page also takes a few minutes with both Mozilla 1.8b1 and Mozilla
1.8b2/20050410.

Comment 3

[Steve England [:stevee]]

This might be the same kind of thing as seen in bug 282851

Comment 4

[wroot]

(In reply to comment #3)
> This might be the same kind of thing as seen in bug 282851

yes, this seems the same. As about tables, i have notice that Nvu (web page
wysiwyg editor based on mozilla composer) have problems processing large tables.
It works very slowly and after some time it's better to restart it, because you
cant work anymore. A table only about 70x5 cells size makes Nvu "hang". I mean,
so small table and Nvu moves like a turtle.

Comment 5

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[wroot]

confirming the same behavior with 1.0.7 version. CPU very high and firefox
freeze after some time.

Comment 7

[Jo Hermans]

(In reply to comment #6)
> confirming the same behavior with 1.0.7 version. CPU very high and firefox
> freeze after some time.

mostly works for me in Firefox 1.5 beta 1, even on a very old and slow Mac. Due
to the same of the table and cells, it's slow ofcourse, but not unusable.

Comment 8

[wroot]

(In reply to comment #7)

> mostly works for me in Firefox 1.5 beta 1, even on a very old and slow Mac. 
 
As i have almost forgotten about this bug, i didnt try it out with 1.5b1 when i
tested Mozilla. Now i just dont want to install beta again. I'll wait till final
1.5 release and test then.

>Due to the same of the table and cells, it's slow ofcourse, but not unusable.

Are you talking about Nvu? Well it just horrible slow and yes it becomes
unusable after some time of working with big tables.

Comment 9

[wroot]

Ok. With my new PC (A64 3200+ and 1GB of RAM) and Firefox 1.5.0.1 this forum thread was loaded flawlessly, only junmped for a 100% once.

Comment 10

[Samuel Sidler (old account; do not CC)]

This loaded fine for me using Firefox 2.0.0.3 on Windows XP SP 2 and Mac OS X 10.4.9. If you can reproduce this with Firefox 2.0.0.3 and do, indeed, get huge load on your processor for an extended period of time, please reopen this bug. I can't reproduce an extended jump and the highest my machine maxed out on was 50% but usually chilled between 18% and 30%.

Comment 11

[wroot]

(In reply to comment #10)
> This loaded fine for me using Firefox 2.0.0.3 on Windows XP SP 2 and Mac OS X
> 10.4.9. If you can reproduce this with Firefox 2.0.0.3 and do, indeed, get huge
> load on your processor for an extended period of time, please reopen this bug.
> I can't reproduce an extended jump and the highest my machine maxed out on was
> 50% but usually chilled between 18% and 30%.
> 

Firefox jumped to a 100% few times in a 4-5 secs. But overall system and browser behaviour wasnt affected by this. Or i just didnt notice this, cause it was just for a sec. On my brother's PC (Duron 900MHz) it was ok for some time, only 80 90 % few times and browser was ok, switching tabs was ok, then for a 10 secs maybe it was 100% and browser was sluggish. But it didnt hang and finally loaded that forum thread (my brother's internet connection is slower than mine too). So i dont know what should i do. This is still causing high CPU usage, especially on old, slower systems. But that forum thread is really huge. Should i reopen this bug?

Comment 12

[Wayne Mery (:wsmwk)]

URL contents appear to have changed. no testcase.

Comment 13

[wroot]

I cant find the new url of that thread, so marking this bug as Invalid (dont know what is better). Havent seen such behaviour anymore.