Browser hangs, cpu usage goes to 99+%




14 years ago
13 years ago


(Reporter: John Harlow, Assigned: Blake Ross)



Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)
Build Identifier: Firefox version 0.9.1

The sequence of page hits (see below strace) produces a (fully) reproducible 
condition which locks up my firefox. When it locks, I see this in strace. 
select(4, [3], NULL, NULL, NULL)        = 1 (in [3]) 
read(3, "\1\1n}\0\0\0\0A\356\0\0015\0\236\0\0\0\0\0\0\0\0\0(\0\0"..., 32) = 32 
write(3, "(\0\4\0\344\v\300\2\216\0\0\0\0\0\0\0", 16) = 16 
read(3, 0xbfffd280, 32)                 = -1 EAGAIN (Resource temporarily 
select(4, [3], NULL, NULL, NULL)        = 1 (in [3]) 
read(3, "\1\1o}\0\0\0\0A\356\0\0015\0\236\0\0\0\0\0\0\0\0\0(\0\0"..., 32) = 32 
write(3, "(\0\4\0\344\v\300\2\216\0\0\0\0\0\0\0", 16) = 16 
read(3, "\1\1p}\0\0\0\0A\356\0\0015\0\236\0\0\0\0\0\0\0\0\0(\0\0"..., 32) = 32 
write(3, "(\0\4\0\344\v\300\2\216\0\0\0\0\0\0\0", 16) = 16 
read(3, "\1\1q}\0\0\0\0A\356\0\0015\0\236\0\0\0\0\0\0\0\0\0(\0\0"..., 32) = 32 
write(3, "(\0\4\0\344\v\300\2\216\0\0\0\0\0\0\0", 16) = 16 
read(3, "\1\1r}\0\0\0\0A\356\0\0015\0\236\0\0\0\0\0\0\0\0\0(\0\0"..., 32) = 32 
gettimeofday({1089132809, 131113}, NULL) = 0 
gettimeofday({1089132809, 131743}, NULL) = 0 
kill(12243, SIGRTMIN)                   = 0 
gettimeofday({1089132809, 132466}, NULL) = 0 
gettimeofday({1089132809, 132565}, NULL) = 0 
gettimeofday({1089132809, 133831}, NULL) = 0 
gettimeofday({1089132809, 159452}, NULL) = 0 
gettimeofday({1089132809, 159603}, NULL) = 0 
kill(12243, SIGRTMIN) 

Reproducible: Always
Steps to Reproduce:
	1.) got to 
	2.) Select "Search" link on left-hand side 
	3.) Enter Goldmine in "Application Name" and press <Submit Search> 
	4.) Choose "Goldmine 6.5"  
	5.) Choose "Search" link on left-hand side 
Actual Results:  
You are now hung. 

Expected Results:  
Should have returned to the Search page and not consumed all of my CPU 

Strace in details above


14 years ago
Severity: normal → critical
Keywords: hang

Comment 1

14 years ago
WFM on WinXP Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040703 Firefox/0.9.0+

Comment 2

14 years ago
WFM, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514

Comment 3

14 years ago
I see from postings it works on windows. Just a bit more on my environment. I am
running SuSE 9.1, with stock (but not latest) kernel (2.6.4-54-5-default). I am
also running mozilla (1.6-72 rpm) and these pages work fine in that release of
mozilla on my system. This firefox install is MozillaFirefox-0.9.1-0.1 from rpm
as well.

Comment 4

14 years ago
I find that this happens most often when using Bittorrent. The specific client 
I am using is BitComet. I have consistently crashed because of this memory 
leak and even have gone so far as reformatting because of it. 


14 years ago
Depends on: 216288

Comment 5

14 years ago
I can't reproduce this with the steps given using firefox 0.9.3 installed from rpms.  I am on Fedora Core 1. 

Comment 6

13 years ago
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050313 Firefox/1.0+
I couldn't reproduce the problem.

Comment 7

13 years ago
John, do you continue to experience this bug? I notice that it's about 10 months
since you posted.
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.