Closed Bug 285998 Opened 20 years ago Closed 19 years ago

extreme system load when closing tabs

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: yoshi3, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050306 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050306 Firefox/1.0.1

closing a tab when the other page is loading in the other tab causes swap usage
go sky-high, memory usage go sky-high and system gets very slow and unresponsive
for a while. this happens with epiphany as well (might be a gecko engine bug)

Reproducible: Always

Steps to Reproduce:
1.open a page in one tab
2.open a different page in second tab
3.close the first tab while the page loads in the other tab

Actual Results:  
system slows down to a crawl (even mouse pointer barely reacts)
swap usage goes up by ~100MB, cpu usage is normal. ram usage goes up somewhat. 
everything returns to normal after ~2min

Expected Results:  
close the tab, and load the page without slowdowns, and extra memory/swap usage.

about:buildconfig

about:buildconfig

Build platform
target
i686-pc-linux-gnu

Build tools
Compiler 	Version 	Compiler flags
gcc 	gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2,
pie-8.7.6) 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align -Wno-long-long
-march=pentium4 -pipe -pthread -pipe
c++ 	gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2,
pie-8.7.6) 	-fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith
-Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy
-Wno-non-virtual-dtor -Wno-long-long -march=pentium4 -pipe -Wno-deprecated
-fshort-wchar -pthread -pipe

Configure arguments
--disable-ldap --disable-mailnews --enable-crypto --disable-composer
--enable-single-profile --disable-profilesharing --enable-optimize=-O2
--enable-old-abi-compat-wrappers --disable-installer --disable-pedantic
--enable-crypto --with-system-jpeg --with-system-png --with-system-zlib
--without-system-nspr --enable-default-toolkit=gtk2 --disable-ipv6
--disable-xinerama --enable-xprint --enable-freetype2 --enable-freetypetest
--disable-debug --disable-tests --enable-reorder --enable-strip
--enable-strip-libs --enable-elf-dynstr-gc --disable-xft --enable-oji
--enable-mathml --disable-jsd --disable-xpctools --enable-gnomevfs --enable-svg
--enable-svg-renderer-cairo
--with-default-mozilla-five-home=/usr/lib/MozillaFirefox
--enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth,-venkman,gnomevfs
--prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --libdir=/usr/lib
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.