Bug 604262 - IcedTea Java plugin crashes
IcedTea Java plugin crashes
Product: Fedora
Classification: Fedora
Component: java-1.7.0-icedtea (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Deepak Bhole
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-06-15 14:24 EDT by Patrick O'Callaghan
Modified: 2010-06-17 05:34 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-17 05:34:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Patrick O'Callaghan 2010-06-15 14:24:38 EDT
Description of problem:
On opening http://select.nytimes.com/premium/xword/puzzles.html with the Chromium browser, I get this message: "The following plug-in has crashed: /usr/lib/java-1.6.0-openjdk-"

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Open http://select.nytimes.com/premium/xword/puzzles.html
2.Crash occurs immediately
Actual results:
Crash in Java plugin

Expected results:
Functioning Java plugin

Additional info:
/var/log/messages shows:

Jun 15 13:49:28 bree kernel: chromium-browse[6405]: segfault at fffffffffffff610 ip 0000003a75c7585c sp 00007fff31363860 error 4 in libc-2.12.so[3a75c00000+175000]

The register values in the message are exactly the same each time.

Also, it's noteworthy that the crash occurs on simply opening the page. It's not necessary to click on any of the Java-powered links it contains, but clicking on these also produces the message.
Comment 1 Patrick O'Callaghan 2010-06-15 14:27:30 EDT
The same crash occurs when visiting java.com and clicking on the Verify Java Version button on http://java.com/en/download/installed.jsp
Comment 2 Patrick O'Callaghan 2010-06-16 01:36:50 EDT
The latest update to Java (1:java-1.6.0-openjdk-plugin- appears to fix this bug. Both test pages now open correctly.

Note You need to log in before you can comment on or make changes to this bug.