Description of problem: firefox crashes on running a signed (OK) java applet from the home banking web site which implements the login form Version-Release number of selected component (if applicable): firefox 10 (both .1 and .2) How reproducible: always, just run the applet Steps to Reproduce: 1. connect to the bank login page 2. click RUN on the applet (OK) signature verification popup 3. Actual results: crash Expected results: login form Additional info: works perfectly fine with firefox 9
Can you check it with an upstream binary package from mozilla.org?
yes, but you should tell me which one and how to download it
I downloaded firefox-10.0.1.tar.bz2 (firefox: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped) from www.mozilla.org, and it works fine
I see. Can you check the 10.0.1 from Fedora updates? (https://admin.fedoraproject.org/updates/FEDORA-2012-1650)
CRASH installed: firefox-10.0.1-1.fc16.x86_64.rpm and xulrunner-10.0.1-1.fc16.x86_64.rpm
Can you please attach content of "about:plugins" from the fedora package and from the upstream binary? Which Java do you use?
Created attachment 561928 [details] about:plugins from upstream binary version
Created attachment 561929 [details] about:plugins from fedora version user-1
Created attachment 561931 [details] about:plugins from fedora version user-2
java-1.6.0-openjdk-1.6.0.0-63.1.11.fc16.x86_64 I uploaded the plugin pages. I noticed that one user on the machine appears as having 2 plugin versions of icedtea-web-1.1.4-4.fc16.x86_64; it is not the user who has the crash who instead has only 1 occurence of icedtea, ie user-2 if I run fedora firefox from the command line I get java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11) (fedora-63.1.11.fc16-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
update: since I was not convinced by my tests, I downloaded the latest upstream binary firefox versions 10.0.2, both i686 and x86_64 (from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/10.0.2-candidates/build1/linux-x86_64/en-US/ ) Now the upstream binary i686 did not find Java (since the installed IcedTea is x86_64) and did not run the applet. Instead the upstream binary x86_64 10.0.2, after a renaming of the x86_64 plugin directory, found all plugins, run the applet and CRASHED
Similar problem for me: xulrunner-10.0.1-3.fc16.x86_64 firefox-10.0.1-1.fc16.x86_64 icedtea-web-1.1.4-4.fc16.x86_64 java plugin enabled in ff - Setting "dom.ipc.plugins.java.enabled;false" to true in about:config has no effect - Applet does not load - If requested java console doesn't appear. - Navigator shows garbage in the applet window - Wow! libflashplayer.so plugin is started but no flash requested! Tested on several java-based pages with no flash nor any other <object> element
Okay, please attach the firefox stractrace: https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Obtain_crash_stack_trace
Created attachment 566549 [details] crash_bt
I did run the crash stack trace (but no debug info table installed) and uploaded the output versions are firefox-10.0.1-1.fc16.x86_64 and xulrunner-10.0.1-3.fc16.x86_64
Can you please install the debuginfo packages (https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products) and attach it again? We need the debug symbols.
Created attachment 566572 [details] crash_bt2 added debuginfo symbols
Can you try to set dom.ipc.plugins.java.enabled to true? in about:config. And do you have any reproducer? (page where it crashes?)
Found that google chrome 17.0.963.56 suffers same problem: java applet doesn't load nor starts So imo the problem is related to icedtea-web plugin, not to FF
sorry to disagree, but I am using chromium-17.0.963.46-3.fc16.x86_64 on the same machine and no crash at all
After setting dom.ipc.plugins.java.enabled to true it works, no more crash. I will test it more later on. For the reproducer, yes I have an URL, but can I send it to you by email ? Thanks
yes, send the reproducer to stransky please, thanks.
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=704249 The crash is caused when JS_NewContext is called off the main thread from js plugin. dom.ipc.plugins.java.enabled works here as a workaround.
Accrding to https://bugzilla.mozilla.org/show_bug.cgi?id=704249 it's fixed in IcedTea-Web 1.2pre.
Just tried with firefox-11.0-1.fc16.x86_64, icedtea-web-1.2-1.fc16.x86_64 and dom.ipc.plugins.java.enabled=false and seems to work fine
I am using Firefox 10.0 and when I click on Java console nothing is coming up. When I open my website I get the error popup saying - Check if your environment allows to download and run Java applets. Refer to the Java console for more details. I did all the settings including dom.ipc.plugins.java.enabled=true. It did not work out. Do I need to install any patch on top of 10.0 version to get this fixed.
(In reply to comment #26) > I am using Firefox 10.0 and when I click on Java console nothing is coming up. > When I open my website I get the error popup saying - Check if your environment > allows to download and run Java applets. Refer to the Java console for more > details. I did all the settings including dom.ipc.plugins.java.enabled=true. It > did not work out. Do I need to install any patch on top of 10.0 version to get > this fixed. Can you please post the out of about:plugins (enter in Firefox location bar and hit enter)?
Enabled plugins Find more information about browser plugins at mozilla.org. Find updates for installed plugins at mozilla.com/plugincheck. Help for installing plugins is available from plugindoc.mozdev.org. Java(TM) Platform SE 6 U11 File: npdeploytk.dll Version: 6.0.110.3 Java(TM) Platform SE binary MIME Type Description Suffixes application/npruntime-scriptable-plugin;DeploymentToolkit Java(TM) Platform SE 6 U11 File: npjp2.dll Version: 6.0.110.3 Java Plug-in 1.6.0_11 for Netscape Navigator (DLL Helper) MIME Type Description Suffixes application/x-java-applet Java Applet application/x-java-bean JavaBeans application/x-java-vm application/x-java-applet;version=1.1.1 application/x-java-bean;version=1.1.1 application/x-java-applet;version=1.1 application/x-java-bean;version=1.1 application/x-java-applet;version=1.2 application/x-java-bean;version=1.2 application/x-java-applet;version=1.1.3 application/x-java-bean;version=1.1.3 application/x-java-applet;version=1.1.2 application/x-java-bean;version=1.1.2 application/x-java-applet;version=1.3 application/x-java-bean;version=1.3 application/x-java-applet;version=1.2.2 application/x-java-bean;version=1.2.2 application/x-java-applet;version=1.2.1 application/x-java-bean;version=1.2.1 application/x-java-applet;version=1.3.1 application/x-java-bean;version=1.3.1 application/x-java-applet;version=1.4 application/x-java-bean;version=1.4 application/x-java-applet;version=1.4.1 application/x-java-bean;version=1.4.1 application/x-java-applet;version=1.4.2 application/x-java-bean;version=1.4.2 application/x-java-applet;version=1.5 application/x-java-bean;version=1.5 application/x-java-applet;version=1.6 application/x-java-bean;version=1.6 application/x-java-applet;jpi-version=1.6.0_11 application/x-java-bean;jpi-version=1.6.0_11 Windows Presentation Foundation File: NPWPF.dll Version: 3.5.30729.1 Windows Presentation Foundation (WPF) plug-in for Mozilla browsers MIME Type Description Suffixes application/x-ms-xbap XAML Browser Application xbap application/xaml+xml XAML Document xaml
Hmm, the list has DLLs. Which OS are you using?
Sorry for the late communication. The OS is Windows Server Standard (Service Pack 1 )
Apologies to you, koteshwarv, but then you're in the wrong place. Fedora cannot fix either your Firefox on Windows, nor your Windows Java runtime.
Hi koteshwarv, as Bill pointed out, we cannot fix anything for Windows in any way. I am going to close this as NOTABUG as it is not a Fedora/RHEL bug.
Oops, the original bug was opened by someone else. Sorry :( Re-opening.
(In reply to comment #25) > Just tried with firefox-11.0-1.fc16.x86_64, icedtea-web-1.2-1.fc16.x86_64 > and > dom.ipc.plugins.java.enabled=false and seems to work fine What happens if the above is not specified? Still crashes?
For me the bug is fixed, all ok with default value of dom.ipc.plugins.java.enabled, no more crashes we can close the ticket, as far as I understand it has been solved upstream, see comment #23
(In reply to comment #35) > For me the bug is fixed, all ok with default value of > dom.ipc.plugins.java.enabled, no more crashes > we can close the ticket, as far as I understand it has been solved upstream, > see comment #23 Fair enough. Thanks!