System lockup w/ FF2.0 and the BACK arrow. Have to force Power down.

RESOLVED INCOMPLETE

Status

()

Firefox
General
--
major
RESOLVED INCOMPLETE
11 years ago
10 years ago

People

(Reporter: Eric Struble, Unassigned)

Tracking

({hang})

2.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: CLOSEME 09/09 (INCOMPLETE))

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9

Firefox Version 2.0 causes my PC to lockup. There is no keyboard or mouse response. Operations will complete in the background but the KB/Mouse are dead. The freeze typicially occurs while selecting the BACK arrow on the navigation bar. V1.5 doesn't display the same problem and is stable on my platform.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1. Using the BACK arrow in the navigation bar.
2.
3.
Actual Results:  
Can go days before locking up, unable to accurately reproduce. When fails, the PC is completely unresponsice to any keyboard or mouce input. Also, breifely pressing should do a safe shutdown of PC, it doesn't. The only way to fix the problem is to force a hard shutdown of the PC.
(Reporter)

Updated

11 years ago
Version: unspecified → 2.0 Branch
Did you try:

- Firefox's safe-mode to exclude extension/theme problems
- a reinstall in a new empty folder
- a new profile? 

http://kb.mozillazine.org/Safe_Mode_(Firefox)
http://www.mozilla.com/en-US/
http://kb.mozillazine.org/Profile_Folder
Keywords: hang
reporter: do you still see the problem with current version? 
Did comment #1 hints help you?
Severity: critical → major
Component: Toolbars → General
QA Contact: toolbars → general
Whiteboard: CLOSEME 09/09 (INCOMPLETE)

Comment 3

10 years ago
No response from reporter.

-> INCOMPLETE
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.