15924 - M10 apprunner does not start on Dutch Win98 w/JDK 1.3beta

Status: VERIFIED DUPLICATE of bug 5369

(Core Graveyard :: Java: OJI, defect, P3)

Description

[Ernst de Haan]

M10 (apprunner.exe) does not start up on my Winblows 98 system, it just blows
away with a General Protection Fault. It uses (or attempt to) JDK 1.3 beta.
M9 ran fine (it started allright).

Following is (1) stdout/stderr output (2) info displayed in the GPF error dialog
(partially in Dutch )-:), (3) the Java console output and (4) details about my
system.

_____________________
stdout/stderr output:

*** Registering html library
Registering DOM Viewer
RegisterSelf([xpconnect wrapped nsIComponentManager],[xpconnect wrapped nsIFileS
pec],rel:nsSample.js,text/javascript)
RegisterSelf done
Java(TM) HotSpot Client VM warning: Setting of property "java.compiler" is ignor
ed
initialization error: Can't load class netscape/javascript/JSUtil
initialization error: Can't read static field java.lang.Void.TYPE
Setting content window
browser.startup.page = 1
startpage = www.mozilla.org

________________________________
Details displayed in GPF dialog :

APPRUNNER heeft een fout met betrekking tot een ongeldige pagina veroorzaakt in
module XPCOM.DLL op015f:60ad1510.
Registers:
EAX=00000000 CS=015f EIP=60ad1510 EFLGS=00010216
EBX=012a0e10 SS=0167 ESP=0063eeb8 EBP=0063efc0
ECX=000000a1 DS=0167 ESI=0063eff0 FS=1f67
EDX=817101fc ES=0167 EDI=0063efec GS=0000
Bytes in CS:EIP:
80 38 00 74 08 50 8b ce e8 1e fa ff ff 5e c9 c3
Stackdump:
0063eff0 00000100 0000010c bff7b9b6 8175ad94 0000010c 780012b1 0000003f 00000100
0000010c bff7b9b6 0000003f 0063ef84 0a33da60 bff7b9b6 8175ad94

_____________________
Java console output:

Java(TM) Plug-in: Version 1.3beta-O
Using JRE version 1.3beta Java(TM) HotSpot Client VM
User home directory = C:\WINDOWS
Proxy Configuration: Browser Proxy Configuration

_______________
System details:

Intel Pentium2-412 MHz
128 MB 103 MHz
Diamond Viper V550
SB Live!
Original Windows 98 (4.10.1998) Dutch version (NL)
JDK 1.3 beta

Comment 1

[Michael Lowe]

Try deleting mozregistry.dat in your c:\windows directory and delete the user50
directory that the previous Mozilla had created.

Comment 2

[Michael Lowe]

From the release notes:

Do not use Java Plugin 1.3. It doesn't work with the most recent mozilla builds,
and crashes will result. Make sure there are no files named *npjava*.* in either
the bin/;lugins directory or the NS4.x plugins directory. This problem is being
addressed. For more information about this bug, see bug 5369

Comment 3

[don]

jar, any idea to whom I should give this bug?  I don't know who handles the JDK
stuff anymore ...

Comment 4

[Jim Roskind]

There are folks actively integrating via OJI.  Warren would know who they are,
and can reassign this bug to them.

Comment 5

[Warren Harris]

I think this should go to Ed Burns.

Comment 6

[don]

Ernst de Haan <[e-mail]> writes:

Hi,
                                                                               I
deleted the mozregistry.dat file, and now M10 starts up. This is
great, guys! How often do you get a quick resolution for a problem on a
_saturday_ ??? {:-)


... so I'm lowering the severity of this bug to major.

Comment 7

[edburns]

This is a manifestation of bug 5369.  Please see that bug for a workaround.

The long and short of it is that you have a JVM with a bug in it to which
mozilla doesn't respond well.  You can either perform the workaround, or update
your JVM (when a version without the bug is publically available).

*** This bug has been marked as a duplicate of 5369 ***

Comment 8

[leger]

Resetting QA contact from leger.