284496 - crashes on entering this site

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Jochen Puchalla]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.3; Linux) KHTML/3.3.2 (like Gecko)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050110 Firefox/1.0 (Debian package 1.0+dfsg.1-2)

Mozilla latest nightly also crashes 

Reproducible: Always

Steps to Reproduce:
1. go to this address 
Actual Results:  
crash 

Expected Results:  
render the page

Comment 1

[Jochen Puchalla]

Maybe a java related problem? 
 
jochen@compi:~ > mozilla/mozilla  
/etc/init.d/xprint: /etc/init.d/xprint: Keine Berechtigung  
INTERNAL ERROR on Browser End: Exec of "java_vm" failed: 2  
<  
System error?:: Datei oder Verzeichnis nicht gefunden  
Gdk-ERROR **: Fatal IO error 9 (Ungültiger Dateideskriptor) on X server :0.0.  
INTERNAL ERROR on Browser End: Could not read ack from child process  
System error?:: Die Ressource ist zur Zeit nicht verfügbar  
  

Comment 2

[Matthias Versen [:Matti]]

Do you crash if you open 
http://www.java.com/en/download/help/testvm.xml ?

Comment 3

[Jochen Puchalla]

FF also crashes on http://www.java.com/en/download/help/testvm.xml .  
I use Java(TM) Plug-in 1.4.2_05-b04 .  
 
Upgrading to 1.5.0_01 resolved the problem. Funny however, about:plugins still 
shows 1.4.2. The applet shows 1.5.0, like Mozilla does. 
Returning to the test page after about:plugins does not work. FF does not show 
its window content then, it freezes somehow. 
 

Comment 4

[Matthias Versen [:Matti]]

that is a plugin installation problem.
Be sure that you didn't copy the plugin (the 1.4.x one) and the symlink isn't
broken.
You should remove the symlink of the 1.4.X PLugin from your Plugins-Dir...

Comment 5

[Jochen Puchalla]

I already removed the old .so in HOME and /usr/..., but I had to remove the 
pluginreg.dat . Then about:plugins was OK. 
Nevertheless reloading the test page makes FF freeze. My symlink is fine. There 
is no more 1.4 version on my hard disk, I checked with updatedb and locate. 
However, now the original bug site works, even reloading it.