Crashes with Java Plugin

RESOLVED INVALID

Status

Core Graveyard
Java-Implemented Plugins
--
critical
RESOLVED INVALID
16 years ago
6 years ago

People

(Reporter: Brian Foddy, Assigned: Igor Kushnirskiy)

Tracking

Trunk
Sun
Solaris

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: java)

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:0.9.8) Gecko/20020310
BuildID:    2002041818

Browser core dumps on startup when Java j2re1.4.0 plugin is installed.
This problem does not occur in 0.9.9 using the exact same machine,
java, and install process.

Sun Solaris 2.8, Sun java j2re1.4.0.

Reproducible: Always
Steps to Reproduce:
1.ln -s /usr/j2re1.4.0/plugin/sparc/ns610/libjavaplugin_oji140.so
plugins/libjavaplugin_oji.so
2.mozilla
3.core dump

Reproducable 100%.  Always works in 0.9.9.

Actual Results:  core dump

I have an example core file, but don't have gdb to easilly get a
backtrace.  I do have Suns debugger, its equivalent bt:

   main(0x0, 0xffbef24c, 0xffbef254, 0x5e608, 0x0, 0x0)
   0x18d34(0x0, 0xff236640, 0x5e8f0, 0x1a6d0, 0x100d4, 0x0)
   CreateHiddenWindow__17nsAppShellService(0x12d2c8, 0xfdf4d1a4, 0x12d2c8,
0xfdf4e490, 0xffbeefd8, 0x1c1e0)
   SetXPConnectSafeContext__17nsAppShellService(0x0, 0x8ad88, 0x8ad48, 0x0, 0x0,
0xffe)
  
GetHiddenWindowAndJSContext__17nsAppShellServicePP20nsIDOMWindowInternalPP9JSContext(0x0,
0xffbeef88, 0xffbeef80,
 0xfdf4de54, 0x0, 0x0)
   assign_from_helper__13nsCOMPtr_baseRC15nsCOMPtr_helperRC4nsID(0xffbeef00,
0xffbeeef0, 0xff36b504, 0xff1f0260,
 0xff3e2668, 0xfdf37c9c)
   __cl__C14nsGetInterfaceRC4nsIDPPv(0xffbeeef0, 0xff36b504, 0xffbeee6c,
0xff1b9f7c, 0xff1a5e78, 0xfdf361e0)
   GetInterface__10nsWebShellRC4nsIDPPv(0xabaf0, 0xff36b504, 0xffbeee6c,
0xfd8d5a14, 0xff3e2668, 0xfdf39fc0)
   EnsureScriptEnvironment__10nsDocShell(0xabaf0, 0xfd8d3d80, 0xff36b504, 0x1,
0x17998, 0x0)
  
NewScriptContext__14nsDOMSOFactoryP21nsIScriptGlobalObjectPP16nsIScriptContext(0xaa7a8,
0xaeec8, 0xabba0, 0xfd824ae0,
 0xabaf0, 0xff3bdd1c)
  
NS_CreateScriptContext__FP21nsIScriptGlobalObjectPP16nsIScriptContext(0xaeec8,
0xabba0, 0x0, 0x0, 0x0, 0x0)
   Init__15nsJSEnvironment(0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
   StartupLiveConnect__12nsJVMManagerP9JSRuntimeRi(0xcb760, 0x1208b8,
0xffbeeb38, 0xfd76f26c, 0xfffffff8, 0x0)
   MaybeStartupLiveConnect__12nsJVMManager(0xcb760, 0x0, 0x0, 0x0, 0x0, 0x0)
   StartupJVM__12nsJVMManager(0xcb760, 0x0, 0x0, 0x0, 0x0, 0x0)
   GetPluginFactory__16nsPluginHostImplPCcPP9nsIPlugin(0x0, 0xfd77bb68,
0xffbee9a8, 0xfd7306c8, 0x1, 0xfd765280)
   JavaPluginFactory5::Create(0x66370, 0xfd5b06fc, 0xd1dfc, 0x0, 0xd1dfc,
0xfd597f48)
   JavaPluginFactory5::JavaPluginFactory5(0xd07b8, 0x66370, 0x13950, 0xfd5af244,
0xfd559ad8, 0xd07b8)
   CPluginServiceProvider::CPluginServiceProvider(0xcaf60, 0x66370, 0x13950,
0xfeb41524, 0xfd559ad8, 0xcaf60)
  0xffe80000(0x66370, 0xfd5afdf4, 0xcaf64, 0x68, 0xd28e8, 0x0)
SUNs problem, not ours
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Whiteboard: java
(Reporter)

Comment 2

16 years ago
On what basis to you claim its Sun's problem?
The EXACT same install, java, etc works fine on
Mozilla 0.9.9 and core dumps on RC1.

Do you have any suggestions to fix the problem?
(Reporter)

Comment 3

16 years ago
On further playing around, I downgraded to Java
j2re_1_3_1_03 plugin, and it works.  However I know
this version failed in past combos either Netscape or Mozilla.
And it only claims to have a NS600 directory, where 1.4 has a 610
directory.

Also I tried 0.9.9 against Java j2re_1_3_1_03 (the same version that
now works in RC1) and it doesn't work.  It won't core dump, but pages
don't see the plugin (even tho the plugins pages says they are there).

So what the obvious questions are there must have been 
recent Java compatibility changes between RC1 and 0.9.9.
What is the recommended Java version for Sun Solaris targeted
for version 1.0?

Thanks,
Brian
Component: Java-Implemented Plugins → Java-Implemented Plugins
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.