Closed Bug 487244 Opened 16 years ago Closed 16 years ago

multiple Java Script Error messages on opening; firefox crashes, often without crash dump - "Java Script Application" "onLookup Failed 55 1"

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: r.buggy, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3 Bug appears similar to bug 469491 found by nobody@mozilla.org On opening Firefox page several error messages are presented (piled on top of each other). They read "Java Script Application" "onLookup Failed 55 1". The number od identical messages varies from a few to a dozen or so. I do not know the reason for varying numbers of messages --- possibly it is relaated to the number of images on the paage. The message boxes can be closed using their "OK" button or the "X" in the upper right corner. When the boxes have been closed sometimes use of Firefox can proceed, sometimes the program crashes without leaving a crash dump. When Firefox proceeds and another web page is opened, the series of error messages is again encountered. On opening, Firefox noted that QuickJava 0,4,2,1 is incompatible with the version of Firefox and was disabled by Firefox. A compatible version of Java was not found. Reproducible: Always Steps to Reproduce: 1.error messages appear always on opening Firefox. 2.Firefox crashes (sometimes but not always) when error boxes are closed. 3. Actual Results: see above
Please reinstall, start in safemode. results?
Summary: multiple Java Script Error messages on opening; firefox crashes, often without crash dump → multiple Java Script Error messages on opening; firefox crashes, often without crash dump - "Java Script Application" "onLookup Failed 55 1"
A Google search tells me this is due to the McAfee SiteAdvisor extension. If you're still seeing it with the current version of that extension, please contact its author.
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.