308855 - firefox uses more than 190 mbytes and gets slow on http://talkback-public.mozilla.org/reports/firefox/FF15x/index.html

Status: VERIFIED INCOMPLETE

(Firefox :: General, defect)

Description

[Andreas Morawietz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050916 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050916 Firefox/1.4

Go to http://talkback-public.mozilla.org/reports/firefox/FF15x/index.html
and click on "Topcrashers by Build"

Now firefox gets very very slow, because the list on that page is very long.
Firefox now uses over 190 mbytes of virtual memory.

I couldn't use firefox anymore, it hangs. I must restart it.


I have windows xp SP1 and 256 MB of virtual memory.


Reproducible: Always

Comment 1

[u63580]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 (No
IDN) Firefox/1.4

Response gets slow, and I get to around 184Mb memory usage.  No hang, though.

Comment 2

[Andreas Morawietz]

Additonal, firefox uses up to 100% CPU while scrolling on that page.
I think, that's too much...

Comment 3

[Mike Duncan]

I see an increase in the memory and CPU needed to view this page (while scrolling) but it does not hang for me either. If I scroll using the scrollbar (instead of the mousewheel) I see 100%, but otherwise I see no more than 45-60% for my CPU usage. But this is probably because the resources needed to render the page. 

I have no idea how this is a Critical bug though. One page does not load and all of the sudden its critical? It probably becomes unresponsive because of hardware more than Firefox.

Here are my hardware stats:
(mduncan:contrib) cat /etc/gentoo-release  
Gentoo Base System version 1.12.0_pre16
(mduncan:contrib) cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 1.80GHz
stepping        : 7
cpu MHz         : 1800.221
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 3547.13

(mduncan:contrib) cat /proc/meminfo 
MemTotal:       514128 kB
MemFree:          6088 kB
Buffers:          7664 kB
Cached:         171164 kB
SwapCached:      65128 kB
Active:         430864 kB
Inactive:        48700 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       514128 kB
LowFree:          6088 kB
SwapTotal:     1020116 kB
SwapFree:       839192 kB
Dirty:              20 kB
Writeback:           0 kB
Mapped:         386092 kB
Slab:            23656 kB
CommitLimit:   1277180 kB
Committed_AS:   517052 kB
PageTables:       1568 kB
VmallocTotal:   516056 kB
VmallocUsed:      1672 kB
VmallocChunk:   514240 kB
(mduncan:contrib) free 
             total       used       free     shared    buffers     cached
Mem:        514128     508040       6088          0       7664     171164
-/+ buffers/cache:     329212     184916
Swap:      1020116     180924     839192
(mduncan:contrib) emerge --search mozilla-firefox-bin
Searching...   
[ Results for search key : mozilla-firefox-bin ]
[ Applications found : 1 ]
 
*  www-client/mozilla-firefox-bin
      Latest version available: 1.5.0.2
      Latest version installed: 1.5.0.2
      Size of files: 38,231 kB
      Homepage:      http://www.mozilla.org/projects/firefox
      Description:   Firefox Web Browser
      License:       MPL-1.1 NPL-1.1

Comment 4

[Andreas Morawietz]

Page changed so I can't reproduce it anymore ...

Comment 5

[Aaron Racine]

Reporter, do you have a new URL you can give us that has caused a similar problem for you?  If so, are you able to reproduce this problem with the latest release of Firefox when using a clean profile?

http://kb.mozillazine.org/Profile_Manager

Comment 6

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

Closing as INCOMPLETE since there's no longer a test URL for this. Note that a lot of the slow downs that might have occurred on a page like the Talkback topcrasher page are fixed or greatly improved on trunk.