Closed Bug 507043 Opened 16 years ago Closed 16 years ago

XP system crash (blue screen) upon Firefox (3.5.1) with Google toolbar (3.0.20090324W).

Categories

(Firefox :: Toolbars and Customization, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: RNAinfo, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 GTB5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 GTB5 After upgrade to Explorer 8.0.6001.18702, the system crashes (blue screen) when I open Firefox (3.5.1). This occurs if Google toolbar (3.0.20090324W) is enabled. It is possible to open Firefox (if the toolbar is disabled before closing the previous time), enable the toolbar, and then restart Firefox. In fact, the blue screen only happens the first time that Firefox is loaded after a restart or shutdown (I have reproduced the problem many times, but can avoid it entirely by using Stand By rather than shut down ("turn off")). The hardware is an ASUS Eee PC. Reproducible: Always Steps to Reproduce: 1. Upgrade to Internet Explorer 8.0.6001.18702 2. Enable Google toolbar 3. Restart the computer. 4. Start Firefox Actual Results: Blue screen system crash. Expected Results: Opened Firefox.
If this only occurs with the google toolbar, that is not an issue for firefox, but for google to sort out. Contacting them on any support forum for the toolbar is a good idea. Though first turn off any other extensions, to see if there may be a conflict between the google toolbar and them.
This is not a Firefox issue and this is no google toolbar issue unless google installs a driver that runs in the kernel space. Firefox itself is a usermode application and can not cause the OS to crash. It can trigger a crash in one of the installed drivers/OS that runs in the kernel mode but that is the fault of the driver/OS/hardware and not Firefox fault. marking invalid /as all Blue Screen or OS freeze bugs)
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.