Closed Bug 144079 Opened 23 years ago Closed 23 years ago

Java 1.4 crashes Moz; 1.3.1 OK

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: robbie_usenet, Assigned: joe.chou)

References

()

Details

(Keywords: crash, stackwanted)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020510 BuildID: 2002051009 I was trying to test the 1.4.0 plugin on my linux kit (RedHat 7.2, Moz 1.0RC1) and I did what worked for other versions, i.e. created a symlink in ~/.mozilla/plugins to j2sdk1.4/jre/plugin/i386/ns610/libjavaplugin_oji140.so But every time I try to start an applet (or even start the Java console) I get browser termination with extreme prejudice. The clue is that I also get an error file plugin_stack.trace which is complaining about ClassNotFound: java.lang.NoClassDefFoundError: com/sun/java/browser/net/ProxyServiceProvider at sun.plugin.AppletViewer.initEnvironment(AppletViewer.java:160) at sun.plugin.navig.motif.Plugin.doit(Plugin.java:152) at sun.plugin.navig.motif.Plugin.start(Plugin.java:96) This seems to be a new class for 1.4 (it's in rt.jar for 1.4.0 but not for 1.3.1) - how come when I use the 1.3.1 plugin everything works fine and when I use the 1.4.0 plugin I get this crash? $JDK_HOME and $JAVA_HOME are pointing to the right place (for 1.4) but I assume that Moz doesn't use these, since 1.3.1 works as it should. Yes, I looked at that Danish site (http://gemal.dk/mozilla/java.html) but I can't run regxpcom for some reason: I just get "Can not initialize XPCOM" Would this make a difference? Just to add a bit more to the mix - it WAS working when I first installed RC1 but had the strange artefact of not being able to place heavyweight windows properly (e.g. popping down an AWT Choice). When I changed the symlink to point to 1.3.1 and then back to 1.4.0 it no longer worked ... [Posted this to n.p.m.java but didn't get any responses] Reproducible: Always Steps to Reproduce: 1.Install clean build of Moz 2.symlink from ~/.mozilla/plugins to {JDK_HOME}/jre/plugin/i386/ns610/libjavaplugin_oji140.so 3.Go to any page containing Java 4.Enjoy the crash Actual Results: Kaboom! Crashed with the file plugin_stack.trace: java.lang.NoClassDefFoundError: com/sun/java/browser/net/ProxyServiceProvider at sun.plugin.AppletViewer.initEnvironment(AppletViewer.java:160) at sun.plugin.navig.motif.Plugin.doit(Plugin.java:152) at sun.plugin.navig.motif.Plugin.start(Plugin.java:96) Expected Results: Displayed the applet ... don't crash I can switch back to JDK 1.3.1 (1.3.1-b24) and everything works fine. It USED to work with JDK 1.4 until I switched to 1.3.1 to test some functionality - then switched back to 1.4 and I have been unhappy ever since. I'm using the Official JDK from Sun (plugin version 1.4.0-b92) I first noticed the problem on RC1 - it also happens with RC2. It may have happened before then, I only started playing around with different plugins with RC1 For more details, see "Description"
Moving to OJI.
Assignee: beppe → joe.chou
Severity: major → critical
Component: Plug-ins → OJI
Keywords: crash, stackwanted
QA Contact: shrir → pmac
try ./run-mozilla.sh ./regxpcom
I have the same problem with java 1.3. I run debian sid with the blackdown runtime environment v1.3, and although it was great for a few weeks, now mozilla just quits immediately I access a site with a java applet.
I have a similar problem with J2se 1.4. 1.3.1 used to work fine. As I did with 1.3.1, I made a symbolic link in Mozilla's plugins directory to J2SE 1.4's jre/plugin/i386/ns610/libjavaplugin_oji140.so. For some reason, Mozilla didn't recognize the existence of Java plugin and prompted me to download the plugin. When I click 'no' (instead of 'ok'), Mozilla got crashed. >try ./run-mozilla.sh ./regxpcom plugins/libjavaplugin_oji140.so I also tried this, but it segfaulted. The stack trace is as following: #0 0x00000000 in ?? () #1 0x403bfb5c in ?? () #2 0x400b4397 in nsNativeComponentLoader::SelfRegisterDll () from ./libxpcom.so #3 0x400b5449 in nsNativeComponentLoader::AutoRegisterComponent () from ./libxpcom.so #4 0x400b2717 in nsComponentManagerImpl::AutoRegisterComponent () from ./libxpcom.so #5 0x400b2917 in nsComponentManagerImpl::AutoRegister () from ./libxpcom.so #6 0x08049574 in nsACString::Cut () #7 0x080498ef in nsACString::Cut () #8 0x08049a03 in nsACString::Cut () #9 0x40180647 in __libc_start_main ( main=0x8049934 <nsACString::Cut(unsigned int, unsigned int)+1452>, argc=2, ubp_av=0xbffed8e4, init=0x80490c8 <_init>, fini=0x8049b7c <_fini>, rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffed8dc) at ../sysdeps/generic/libc-start.c:129 The version of Mozilla I'm having this problem with is 1.1beta (2002072204)
>try ./run-mozilla.sh ./regxpcom plugins/libjavaplugin_oji140.so I also tried this, but it segfaulted. The stack trace is as following: >try ./run-mozilla.sh ./regxpcom This ran without any output, but it didn't change the behavior of Mozilla w.r.t. Java plugin. I also tried the latest nightly(2002-08-07) and the talkback agent showed up (Mozilla died) when I declined to install Java plugin and tried 'about plugin'. All other plugins are recognized correctly by Mozilla and are listed in 'about plugin' (when I go to help|about plugin before declining to install Java plugin) but J2SE 1.4 plugin isn't listed. I also tried using ns600 plugin instead of ns610 plugin (because in bug 99829 and bug 148404, some people wrote that ns600 plugin worked for them while ns610 didn't. These bugs are not, however, for Linux but for Solaris).
After upgrading my J2SE from 1.4.0beta3 to 1.4.0 (released), it works fine for me. I remember someone commented that J2SE 1.4.0beta(1,2,3) don't work (in Java related bug for Solaris build) while 1.4.0(released) works. I thought mine was 1.4.0(released) until I ran 'java -version'.
Reporter could you try an updated version of JRE, and comment back. If it works then please resolve this as WORKSFORME
See bug #163253 as a reference.
Works fine now with updated JDK (1.4.0_01 or 1.4.1-beta)
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
QA Contact: pmac → petersen
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.