Closed Bug 216989 Opened 22 years ago Closed 22 years ago

When accessing above site w/1.4 browser immediately crashes.

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: thorn, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Problem occurs only w/1.4 Mozilla. Earlier versions access the above site OK. Thought it might be due to the site having been generated w/MS Frontpage, but not sure. Recently upgraded my OS to RH 9 from RH 8, but problem occurred in RH 8, as well. Reproducible: Always Steps to Reproduce: 1.type in url, or access via bookmark 2. 3. Actual Results: Mozilla immediately terminates/crashes Expected Results: Displayed the page.
Works For Me in the latest nightly, other than telling me I don't have java installed, and works fine in 1.5a. Is it possible this is a problem with java? I know I had a problem with a bad java installation crashing the browser. Try going to another java enabled page (http://www.randomthoughts.net/games/diib/ is one off the top of my head)
Summary: When accessing above site w/1.4 browser immediately crashes. → When accessing above site w/1.4 browser immediately crashes.
site uses fphover applet, which is known to crash Sun's JRE 1.3.x. Upgrading to Sun's JRE (or Blackdown) JRE 1.4.2 will fix your issue. Please reopen if you still crash after upgrading. *** This bug has been marked as a duplicate of 57372 ***
Severity: normal → critical
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Component: Browser-General → OJI
Keywords: crash
Resolution: --- → DUPLICATE
I have upgraded to JRE 1.4.2 and still have the same problem.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Did you follow the JRE installation instructions? http://plugindoc.mozdev.org/javalinux.html (symlink, don't copy... use proper version for your compiler)
symlink was pointing to the wrong folder. Changed it to the gcc3.2 folder and now works fine.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → FIXED
not "fixed"
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
-> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.