Closed Bug 515343 Opened 15 years ago Closed 13 years ago

System / OS hangs for a number of seconds when browser is closed after browser has been running a long time

Categories

(Firefox :: General, defect)

3.5 Branch
x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: walka, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2011-2-25])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)

When firefox has been running for a long time and is closed - the OS hangs/freezes for a number of seconds (more than 5 and less than 30, but different each time)

When closing the browser the browser window disappears as expected and system responds correctly for one or 2 seconds before the mouse freezes, any sound playing 'stutters' for the duration of the freeze and no input can be made from keyboard. This continues for the full length of the 'freeze' until system returns to normal with no other apparent adverse affects. The system has returned to normal every time after a freeze and has not required a restart.

Reproducible: Always

Steps to Reproduce:
1. leave firefox open for a long time (eg overnight so 6 to 8 hours)
2. close browser completely

Actual Results:  
System freezes for a number of seconds after browser window has closed.

Expected Results:  
Mouse, keyboard, sound etc should continue to operate normally on exiting browser.

Does not seem linked to the number of tabs open in the browser - have reproduced this problem with one blank tab as well as one or more tabs with websites open.

Does not seem linked to a specific website running at the time.

Happens only after the last instance of firefox closes, not when a second 'window' of firefox is closed after a long period.

'Long time' - can't quantify how long this is - browser seems to close normally after a couple of hours operation although occasionally has resulted in a brief freeze - a subjective opinion is the freezes are generally longer in proportion to the length of time a browser has been running. Happens every time the browser has been left open for a number of hours (over night or longer) which ranges from 4 hours to more than 24 hours running.

I would have listed it as critical (how long does an average user wait to hit the reset button?) as the freezes are symptomatic of a crash requiring a hard reset however experimenting has shown waiting long enough will allow the system to return to normal.
Does this also happen in safe-mode? http://support.mozilla.com/en-US/kb/Safe+Mode
And with a new profile: http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile ?
Version: unspecified → 3.5 Branch
(In reply to comment #1)
> Does this also happen in safe-mode?
> http://support.mozilla.com/en-US/kb/Safe+Mode
Have not tried it in safe mode - will give it a try but not sure when as laptop is used for work 6 nights a week.
> And with a new profile:
> http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile ?
I will try this some time also when I get a break in work - but additional info, it started from browser updated to 3.5.2
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.