281676 - Get 100% CPU if a tool (for any reason) stops the URL launched in background (to get news, etc.)

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Xabier]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; es-ES; rv:1.7.5) Gecko/20041210 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; es-ES; rv:1.7.5) Gecko/20041210 Firefox/1.0

I've noticed that just opening the browser, FireFox launches in silent mode
several HTTP requests, i.e.
http://news.bbc.co.uk/rss/newsonline_world_edition/front_page/rss091.xml,
apparently to retrieve information that afterwards the user can have available
in the PC directly. It looks to be a way to forward rutinary requests. OK, but
in case any tool detects, and if necessary cuts or blocks this requests, after
some few seconds (1 minute approximately) FireFox start consuming 100% of the
CPU. It looks like its source code enters in an endless loops because of not
being receiving any answer from the socket where the original request was set in. 

Reproducible: Always

Steps to Reproduce:
1.Set up a firewall or tools that cuts any HTTP requests.
2.Launch FireFox. 
3.After a while, since the silently forwarded request is not satisfactorily
retrieved, the 100% use of CPU happens.

Actual Results:  
The same symptom.

Expected Results:  
Whatever the reason is, in case FireFox is not getting an expected answer it
should treat the status of the socket, as well as validate the obtain response
in recv, since otherwise endless loop situations like this could come up.

Comment 1

[Jeff F.]

ok, BIG problem, this should possibly be classified as a blocker.(this may need
another topic line) go to my attachment and press go. It caused my video driver
to enter en endless loop, bringing me to the bsod. not only on mine,but my
freinds too. THIS CRASHED WINDOWS XP. not just the browser. though on computers
that it does not crash it crashes fx.

Comment 2

[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 3

[Gervase Markham [:gerv]]

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.