[edgy] Firefox crashes after opening www.eboost.it

Bug #67232 reported by Giuseppe Iuculano
10
Affects Status Importance Assigned to Milestone
sun-java5 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Firefox crashes after opening http://www.eboost.it

Revision history for this message
John Vivirito (gnomefreak) wrote :

What version of firefox are you using? What version of Ubuntu? Do you have sun-java5-plugin installed or bin or jre? If its installed do you have it set in update-alternatives --config java to use java 1.5 instead of gcj? Can you please provide a backtrace of the crash. You can do this a number of ways you can install firefox-dbg at command prompt tyoe dbg firefox than at the > type run and save it to a file. or if you are using edgy look in /var/crash for a firefox crash report/log.

Changed in firefox:
status: Unconfirmed → Needs Info
Revision history for this message
ville palo (vi64pa) wrote :

I can confirm this. This is reproducible on edgy (ff2.0) and dapper(ff1.5.0.7).
java5-plugin is installed and used. I'll attach dbg traces later

Changed in firefox:
status: Needs Info → Confirmed
Revision history for this message
ville palo (vi64pa) wrote :

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb1a50f29, pid=6931, tid=2973993888
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_08-b03 mixed mode, sharing)
# Problematic frame:
# C [libfontmanager.so+0x3ef29] Java_sun_font_FileFont_getGlyphImage+0x19
#
# An error report file with more information is saved as /tmp/hs_err_pid6931.log
[thread -1318638688 also had an error]
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
INTERNAL ERROR on Browser End: Plugin instance index out of bounds -16449

Revision history for this message
Giuseppe Iuculano (giuseppe-iuculano) wrote :

John,

I'm using firefox 2.0 rcX (edgy version), and sun java:

ii sun-java5-bin 1.5.0-08-0ubuntu1
ii sun-java5-jdk 1.5.0-08-0ubuntu1
ii sun-java5-jre 1.5.0-08-0ubuntu1
ii sun-java5-plugin 1.5.0-08-0ubuntu1

~# update-alternatives --display java
java - status is manual.
 link currently points to /usr/lib/jvm/java-1.5.0-sun/jre/bin/java
/usr/lib/jvm/java-1.5.0-sun/jre/bin/java - priority 53
 slave java.1.gz: /usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre/man/man1/java.1.gz
/usr/lib/jvm/java-gcj/jre/bin/java - priority 1041
 slave java.1.gz: /usr/lib/jvm/java-gcj/man/man1/java.1.gz
/usr/bin/gij-wrapper-4.1 - priority 41
 slave java.1.gz: /usr/share/man/man1/gij-wrapper-4.1.1.gz
Current `best' version is /usr/lib/jvm/java-gcj/jre/bin/java.

Revision history for this message
Jeff Greene (jeffgreene) wrote :

I have narrowed down the crash in firefox to this short segment of code:
              <applet code="Clock.class" width=185 height=13>

                <param name="FontFamily" value="">

              </applet>
I tested it with another class, but it only crashed with Clock.class. If I remove this line:
<param name="FontFamily" value="">
it will not crash Firefox.

Revision history for this message
Jeff Greene (jeffgreene) wrote :

This is really a Java bug, not a firefox one.

Revision history for this message
Jeff Greene (jeffgreene) wrote :

This is really a Java bug, not a Firefox one.

Revision history for this message
magilus (magilus) wrote :

Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs which you find.

Changed in sun-java5:
status: Confirmed → Rejected
Matthias Klose (doko)
Changed in sun-java5:
status: Rejected → Confirmed
Revision history for this message
Jeff Greene (jeffgreene) wrote :

Martin, please do not mark duplicate bugs as "Rejected" as it creates bug mail noise, and makes it more difficult to un-duplicate the bug later if that turns out to be necessary. (Paraphrased from https://wiki.ubuntu.com/Bugs/HowToTriage)

Revision history for this message
magilus (magilus) wrote :

Matthias already pointed me on this. I am very sorry and it will not happen again.

Isn't the noise generated anyway because of the response?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.