467048 - 'Stopped' status is sometimes set once I enter some URL

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Yuri]

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.0.4) Gecko/2008111407 Firefox/3.0.4
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.0.4) Gecko/2008111407 Firefox/3.0.4

I keep seeing this problem for a long time, it was there in 2.X series.

Sometimes firefox gets into some strange state and some URL that I type and press <ENTER> on causes status to be set to 'Stopped'. After this nothing happens. Once I hit reload or press <ENTER> again 'Stopped' status is set again.
After a while problem goes away and URL is loaded. But later I see this problem again on some other URL.

'Stopped' status should only be set when user hits 'Stop' button.

This doesn't happen all the time, but rather in <1% of cases.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Yuri]

This is the major problem with browsing with Firefox and needs to be fixed.

Comment 2

[Popa David]

I wanted to report this aswell. Until this will be fix I will no longer use Firefox.

Comment 3

[Yuri]

I am making it critical trying to attract attention of the FF team.

This is really a major problem with browsing that causes delays in browsing and causes me to switch to Opera so often.
What does FF team think about this?

Comment 4

[Keith]

Adding this comment for the benefit of other developers having the same problem I was.  At first it looked like this bug was the cause.   Maybe I'll save someone a few hours:

I was getting this "Stopped" message in the status bar when setting the URL, as follows, in response to some key events:

window.location.href="some url";

When the key event was 'Escape' the above does not work in Firefox, although it will work in other browsers.  I found that if I call "preventDefault()" on the event first, it WILL then work in Firefox.

Comment 5

[Yuri]

I see this in the current version: 3.5.10.
Bug was first reported 1.5 years ago.

Maybe I would change the request a bit: FF should expand the status "Stopped" with the actual reason why it is stopped. Like "Stopped by user", "Stopped (resources temporarily unavailable)", "Stopped (exceeded network bandwidth limit)"

User should know why it is stopped. Otherwise this message is confusing.

Comment 6

[Tyler Downer [He/Him]]

Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.

Comment 7

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 8

[Yuri]

Yes, this is still happening in 3.6.13.

Instead of just asking "Please confirm its still happening" please look for status "Stopped" and update it so it will say why it is stopped.

It should be on of "Stopped by user", "Stopped due to ..."  and explain the reason since it gets stopped by FF itself without an explanation.

This is the major uncleanliness that exists in FF for years.

Comment 9

[Wayne Mery (:wsmwk)]

Does it happen in newer version?

If stopped status is a hang, please attach file to bug with stacktrace 
https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report#Mac

Comment 10

[Phoenix]

Resolved per whiteboard