Mozilla crashes when accessing this page

RESOLVED WORKSFORME

Status

--
critical
RESOLVED WORKSFORME
16 years ago
8 years ago

People

(Reporter: les_hartzman, Assigned: joshua.xia)

Tracking

({crash, stackwanted})

Trunk
x86
Linux
crash, stackwanted

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

The given URL is for a 'print' version of an article at Javaworld, whose initial
page is http://www.javaworld.com/javaworld/jw-12-2002/jw-1227-sort.html?

When clicking on "Printer-friendly version" (which would give the problem URL),
all of Mozilla dies.  I can bring up the page using Konqueror.

Mozilla on Windows (XP) works for this page.  Also 1.2.1.

Reproducible: Always

Steps to Reproduce:
1.Go to http://www.javaworld.com/javaworld/jw-12-2002/jw-1227-sort.html?
2.Click on "Printer-friendly version"
3.

Actual Results:  
Mozilla closed and died.

Expected Results:  
Not closed and died.

Comment 1

16 years ago
Reporter: Is your JRE plugin properly installed?   (Symlinked, not copied)

Comment 2

16 years ago
wfm using build 20030112 on Linux + JRE 1.4.1_01.
Assignee: asa → joshua.xia
Component: Browser-General → OJI
Keywords: crash, stackwanted
QA Contact: asa → petersen
(Reporter)

Comment 3

16 years ago
As far as I know the JRE is correctly installed.  I'm using SUSE 8.1 Pro.  I
know that the JDK is symlinked.

Comment 4

16 years ago
WFM
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3b) Gecko/20030113
(Reporter)

Comment 5

16 years ago
OK. I reconfigured the plugin installation and now the page is working.  I also
verified that the plugin is symlinked, NOW.  Thanks.

Comment 6

16 years ago
reporter said WFM
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME

Updated

8 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.