Closed Bug 394122 Opened 17 years ago Closed 15 years ago

Crash at windowsupdate.62nds.com / windizupdate.com

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: scott001, Unassigned)

References

()

Details

(Whiteboard: closeme 2009-07-14)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007082822 Minefield/3.0a8pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007082822 Minefield/3.0a8pre

Recent Crasher, I haven't determined the regression window yet.

Reproducible: Always

Steps to Reproduce:

Actual Results:  
Instant crash

Expected Results:  
Not crash
Unconfirmed but it appears to have regressed between 2007082819 and 2007082822
don't crash here
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007082911 Minefield/3.0a8pre
I don't crash either. Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a8pre) Gecko/2007082618 Minefield/3.0a8pre
Ok correction it definitely did not regress between those periods, a few days before.. The crash is also not from the page it self but from the plugin.

Can someone please confirm? (the plugin is fairly safe I believe).
What plugin?
do you still see this problem using FF 3.5 beta**, or latest update of FF 3.0 started in safe mode***?

If yes, please comment
If not, please close with resolution set to WORKSFORME. Or INVALID (if problem was extension or the like)

** http://www.mozilla.com/en-US/firefox/all-beta.html
*** http://support.mozilla.com/en-US/kb/Safe+Mode
Whiteboard: closeme 2009-07-14
No reply, INCO. Please reopen if you still see this bug in Firefox 3.5 or later in Firefox safe mode (http://support.mozilla.com/en-US/kb/Safe+Mode) or a new Firefox profile (http://support.mozilla.com/en-US/kb/Profiles) with updated plugins.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.