Bug 488345 - java.com web site kills firefox
Summary: java.com web site kills firefox
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 10
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-03 20:07 UTC by Tom Horsley
Modified: 2018-04-11 15:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 08:56:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Lots of rpm and backtrace info (48.82 KB, text/plain)
2009-03-04 18:58 UTC, Tom Horsley
no flags Details

Description Tom Horsley 2009-03-03 20:07:09 UTC
Description of problem:

Goto java.com in 64 bit firefox. See a big button that says "Download Java"
and underneath that big button a link for "What Java Do I Have?" (or
something to that effect). Click on the link for testing current java version,
see the page that takes you to start to draw, then Blip! the firefox
window disappears.

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

These may all be relevant since I'm not sure what is blowing up:

firefox-3.0.6-1.fc10.x86_64
java-1.6.0-openjdk-demo-1.6.0.0-9.b14.fc10.x86_64
ldapjdk-4.18-1.fc9.x86_64
java-1.6.0-openjdk-plugin-1.6.0.0-9.b14.fc10.x86_64
java-1.6.0-openjdk-1.6.0.0-9.b14.fc10.x86_64
java-1.6.0-openjdk-devel-1.6.0.0-9.b14.fc10.x86_64
nspluginwrapper-1.3.0-2.fc10.x86_64
nspluginwrapper-1.3.0-2.fc10.i386

How reproducible:

Every time I click on that link.

Steps to Reproduce:
1. see above
2.
3.
  
Actual results:

firefox crash

Expected results:

some information about my java version

Additional info:

This is a pretty freshly installed and updated fedora 10 x86_64 box, I
haven't screwed around with tweaking many things yet, so this is apparently
"out of the box" behavior.

Comment 1 Matěj Cepl 2009-03-04 15:17:44 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

First of all, could we get output of the command

	rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*

Please also install firefox-debuginfo (debuginfo-install is from
yum-utils package).

	debuginfo-install firefox

Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run

	(gdb) thread apply all backtrace

This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Tom Horsley 2009-03-04 18:58:39 UTC
Created attachment 334031 [details]
Lots of rpm and backtrace info

I see gdb complaining about other libs loaded with no debuginfo, but perhaps
there was enough to see what is going on (looked like it called the nasty
old routine at address zero that causes so much trouble for everyone).

Comment 3 Tom Horsley 2009-03-12 22:34:06 UTC
I noticed a few firefox related updates come in and I tried visiting
java.com again. It seems to work OK now with no sudden disappearing act.

Here's the current set of rpms I have that matches the patterns above:

zooty> rpm -qa '*xulrun*' '*firefox*' '*mozilla*' '*flash*' '*plugin*'
gstreamer-plugins-flumpegdemux-0.10.15-4.fc10.x86_64
anaconda-yum-plugins-1.0-3.fc10.noarch
plymouth-plugin-solar-0.6.0-0.2008.11.17.3.fc10.x86_64
plymouth-system-plugin-0.6.0-0.2008.11.17.3.fc10.x86_64
gutenprint-plugin-5.2.3-3.fc10.x86_64
firefox-3.0.7-1.fc10.x86_64
mozilla-filesystem-1.9-2.fc10.x86_64
konq-plugins-4.1.3-2.fc10.x86_64
nspluginwrapper-1.3.0-2.fc10.i386
xulrunner-1.9.0.7-1.fc10.x86_64
java-1.6.0-openjdk-plugin-1.6.0.0-9.b14.fc10.x86_64
xulrunner-devel-1.9.0.7-1.fc10.x86_64
PackageKit-gstreamer-plugin-0.3.14-1.fc10.x86_64
flash-plugin-10.0.22.87-release.i386
kipi-plugins-0.2.0-0.14.rc1.fc10.x86_64
nspluginwrapper-1.3.0-2.fc10.x86_64
plymouth-plugin-label-0.6.0-0.2008.11.17.3.fc10.x86_64
gstreamer-plugins-base-0.10.21-2.fc10.x86_64
PackageKit-yum-plugin-0.3.14-1.fc10.x86_64
totem-mozplugin-2.24.3-1.fc10.x86_64
gstreamer-plugins-good-0.10.13-1.fc10.x86_64

Comment 4 Bug Zapper 2009-11-18 11:16:23 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-12-18 08:56:33 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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