Java JRE broken in FF 3.6.14 [pogo.com]

RESOLVED FIXED

Status

()

Core
Plug-ins
--
major
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: Steve Snyder, Assigned: smichaud)

Tracking

({common-issue+, regression})

1.9.2 Branch
x86
Windows 7
common-issue+, regression
Points:
---

Firefox Tracking Flags

(blocking1.9.2 .17+, status1.9.2 .17-fixed)

Details

(URL)

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
Build #1 of Firefox 3.6.14 breaks the Java Runtime Environment, at least on Win7 32bit with JRE v6u23 installed.

My wife reported that the Java games at pogo.com would stop working after a short time of playing.  This did not happen with 3.6.13 (also with JRE 6u23).

Here's a simpler test.  

1. Go to http://www.java.com/en/download/testjava.jsp
2. Note that the Java information shown by the applet is correct and that the animated coffee cup is seen.
3. Reload the page several times, either by selecting from a bookmark or hitting the Reload button.
4. The applet will stop working. Close the tab with the applet and run the applet again in another tab.  Still doesn't work.

Only by restarting Firefox will Java applets again work.
(Reporter)

Comment 1

7 years ago
When I start v3.6.14, then immediately open the Error Console, I see this already logged:

Error: Components.classes['@mozilla.org/oji/jvm-mgr;1'] is undefined
Source File: chrome://javaconsole1.6.0_23/content/ffjcext.js
Line: 33

I run the applet above once and the Java Console is opened.  No errors seen in the console, and the applet appears to run correctly.

On the 2nd run of the applet, this appears in the Java Console:

Your Java configuration is as follows:<br/> <br/>Vendor: <b><a href="http://java.com">Sun Microsystems Inc.</a></b><br/>Version: <b>Java SE 6 Update 23</b><br/>Operating System: <b>Windows XP 5.1</b><br/>Architecture:  <b>x86</b>
Obj:1.6.0_23
Exit worker loop
java.net.MalformedURLException: no protocol: TestVM2-test.jar
	at java.net.URL.<init>(Unknown Source)
	at java.net.URL.<init>(Unknown Source)
	at sun.plugin.util.GrayBoxPainter.setProgressFilter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.setupGrayBoxPainter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.access$600(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
exception: name.
java.lang.IllegalArgumentException: name
	at sun.plugin2.applet.Applet2ClassLoader.addJar(Unknown Source)
	at sun.plugin2.applet.Applet2Manager.loadJarFiles(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Exception: java.lang.IllegalArgumentException: name

Now I have a black rectangle in the browser window where the applet should be shown. Each subsequent attempt to run the applet results in another copy of the error text shown in the Java Console.

Neither of these errors is seen with Firefox v3.6.13.
OS: Other → Windows 7

Comment 2

7 years ago
(In reply to comment #0)
> Build #1 of Firefox 3.6.14 breaks the Java Runtime Environment, at least on
> Win7 32bit with JRE v6u23 installed.
> 
> My wife reported that the Java games at pogo.com would stop working after a
> short time of playing.  This did not happen with 3.6.13 (also with JRE 6u23).
> 
> Here's a simpler test.  
> 
> 1. Go to http://www.java.com/en/download/testjava.jsp
> 2. Note that the Java information shown by the applet is correct and that the
> animated coffee cup is seen.
> 3. Reload the page several times, either by selecting from a bookmark or
> hitting the Reload button.
> 4. The applet will stop working. Close the tab with the applet and run the
> applet again in another tab.  Still doesn't work.
> 
> Only by restarting Firefox will Java applets again work.

i am having the same issue.
(Reporter)

Comment 3

7 years ago
Yet nobody seems interested.

Oh, well.  I guess I'll be skipping 3.6.14 in favor of the 3.6.15 chemspill release.

Comment 4

7 years ago
here is a reduced test case for this bug:

http://gs3.flyordie.com/FF3614/index.html

the second time the applet tries to start java plugin displays an exception:
java.lang.IllegalArgumentException: name
	at sun.plugin2.applet.Applet2ClassLoader.addJar(Unknown Source)
	at sun.plugin2.applet.Applet2Manager.loadJarFiles(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

Ok, this might be a bug in the Java Plugin, however, the problem started with 3.6.14

Comment 5

7 years ago
Shouldn't this be a blocker for 3.6.14 and/or have keyword "regression" to get enough attention by the devs? Perhaps someone with enough bugzilla powers can change this.

Comment 6

6 years ago
With Namoroka (today's nightly), I get:

Java Plug-in 1.6.0_24
Using JRE version 1.6.0_24-b07 Java HotSpot(TM) Client VM
----------------------------------------------------
exception: Permission denied: null.
java.lang.SecurityException: Permission denied: null
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Exception: java.lang.SecurityException: Permission denied: null
java.net.MalformedURLException: no protocol: A.zip
	at java.net.URL.<init>(Unknown Source)
	at java.net.URL.<init>(Unknown Source)
	at sun.plugin.util.GrayBoxPainter.setProgressFilter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.setupGrayBoxPainter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.showAppletException(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

Could this give any hints to the underlying problem?
I can also reproduce comment #1 with the same error.

Note that I'm using JRE 1.6.0_24.

Comment 7

6 years ago
Also, this is probably filed to the wrong Product/Component combo.
#619349, for example, is under Plugins/Java (Sun).

Comment 8

6 years ago
Well, after Firefox auto-updated all of our customer's computers to 3.6.14, this bug has completely broken their ~$20,000 HVAC graphics control systems. Anybody using the Tridium Niagara R2 framework to control their buildings can no longer use Firefox.

I'm somewhat curious how such a huge bug in such an essential piece of web technology could have been released into the wild after knowing about it for over a month.

exception: Permission denied: null.
java.lang.SecurityException: Permission denied: null
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Exception: java.lang.SecurityException: Permission denied: null
java.net.MalformedURLException: no protocol: /tridium/web/gxpub.jar
	at java.net.URL.<init>(Unknown Source)
	at java.net.URL.<init>(Unknown Source)
	at sun.plugin.util.GrayBoxPainter.setProgressFilter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.setupGrayBoxPainter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.showAppletException(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
I am running XP, FF3.6.14, JRE build 1.6.0_23-b05 when pogo games don't work. As mentioned, this does work with IE8.  My wife just updated to FF3.6.14 using VISTA and she's experiencing the same problem.  Wish there was a way to go back to FF3.6.13.....
Keywords: regression
Duplicate of this bug: 638135
Summary: JRE broken in FF 3.6.14 Build 1 → Java JRE broken in FF 3.6.14 [pogo.com]
This is being reported by many users on SUMO who have updated to 3.6.14.
Keywords: common-issue+

Updated

6 years ago
Assignee: nobody → smichaud

Comment 12

6 years ago
Likely candidates include bug 620773 and bug 611910

Comment 13

6 years ago
Ok, based on the above comments (comment 1,6,8) the plugin is passing in a malformed URL and we are now throwing an exception...so this is fallout (perhaps desired) from bug 611910
I will need to look into this fairly deeply before I can speculate about it.

I hope the STR from comment #0 are actually reproducible.  I'll find out tomorrow.

Comment 15

6 years ago
I tried a build from 2010-12-25 (based on https://bugzilla.mozilla.org/show_bug.cgi?id=620773#c35) and it worked.

 Looks like it is certainly caused by bug 611910 (to make things more confusing, the bugs in https://bugzilla.mozilla.org/show_bug.cgi?id=620773#c35 are reversed...bug 620773 landed in 2011, see https://bugzilla.mozilla.org/show_bug.cgi?id=620773#c23)
Caused by 620773, you mean? The different error in bug 620773 comment 37 does, however, look like it was caused by bug 611910.

Updated

6 years ago
Blocks: 638382

Comment 17

6 years ago
We have an increasing number of Firefox users that cannot log on to our online banking due to the FF 3.6.14 / JRE error.

Since this potentially affects 1,000,000+ eBanking users, some help would be greatly appreciated...

Java console:
**************************************

exception: Permission denied: https://ebanking.sampopankki.fi/html/java/GWPKI/SAM/.
java.lang.SecurityException: Permission denied: https://ebanking.sampopankki.fi/html/java/GWPKI/SAM/
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Exception: java.lang.SecurityException: Permission denied: https://ebanking.sampopankki.fi/html/java/GWPKI/SAM/

**************************************

Comment 18

6 years ago
This is also an issue on 4.0.12 Beta

Comment 19

6 years ago
This is a severe issue.

And very easy to reproduce:
1. Go to any applet like http://java.sun.com/applets/jdk/1.4/demo/applets/DitherTest/example1.html
2. Reload the applet in the same tab: breaks with "java.lang.SecurityException: Permission denied: null"

I cannot believe this bug actually found it's way to the public release.
Java applet support essentially got removed in 3.6.14.

You should:
1. stop delivering 3.6.14 immediately to reduce the damage
2. fix the bug and launch 3.6.15 asap
3. review your qa process to avoid future bugs like this one

Comment 20

6 years ago
At least provide a download link to version 3.6.13 that we can post on our logon pages, so that customers can downgrade until the issue is fixed.

Comment 21

6 years ago
@Thomas:
You can still download 3.6.13 on http://download.mozilla.org/?product=firefox-3.6.13 
If you recommend the old version to your customers you should consider that this version has some critical security flaws which got fixed in 3.6.14

Comment 22

6 years ago
Unfortunately, logging on takes priority over security flaws at the moment.

Comment 23

6 years ago
Also on Win7, 64 bit using 32bit FF+JRE.
Blocks: 638070

Updated

6 years ago
Duplicate of this bug: 638329

Updated

6 years ago
Blocks: 638114
I can't reproduce this bug using the steps-to-reproduce from comment
#0.  I tested with FF 3.6.14 on Windows XP (fully patched) with the
latest Java 6 from Oracle (v6u24).

Anyone else able to reproduce this on Windows XP?

(I have a copy of Windows 7, but I haven't yet installed it.  So it'll
be at least a few hours before I can test on Windows 7.)

But now I see that 638329 was reported on Windows XP.  I'll comment
further there.

Comment 26

6 years ago
I have two machines here with a fully patched Windows XP with Java 6u24 and FF 3.6.14 and the Java applets are not working as described in comment #0 and comment #1

The error messages are variable depending on which applet you are trying.
Do these problems happen when you start Firefox in Safe Mode?  (To do
that, choose Mozilla Firefox (Safe Mode) from the Start menu.)

Comment 28

6 years ago
answer to comment 27. i restarted firefox in safemode, i logged into pogo, launched a game, and it errored out the same way.

Comment 29

6 years ago
@Steven

This issue was reported by a customer on 3 XP machines with Java version 1.6_021 and 1.6.0_24.

We can reproduce this on all kind of machines XP, Vista, Win7.

As already reported this seems not limited to specific applets, it seems to affect all applets, even very simple ones. Just try this http://www.w3.org/People/mimasa/test/object/java/clock and reload a few times using the "Reload" button. Watch the Java console!

Again, this is in no way limited to Windows 7. It also happens with XP.

I really hope that you understand the severe impact this bug is having! I totally agree with axianx and Warren that I can't understand how 3.6.14 could be released with this bug, even though this bug was already reported in January!

Comment 30

6 years ago
It is not even limited to Windows.  I'm seeing the same behavior on Mac OS X 10.6, Firefox 3.6.14, Java 1.6.0_22.

Comment 31

6 years ago
A bug has also been opened in the Java SE bug tracking system and are also looking into it from the Java SE side. 
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7024306
(this link will not work until later tonight)

-Roger
> It is not even limited to Windows.  I'm seeing the same behavior on
> Mac OS X 10.6, Firefox 3.6.14, Java 1.6.0_22.

Interesting.  Does your FF 3.6.14 distro contain the bundled copy of
the Java Embedding Plugin that comes with it (in its
Contents/MacOS/plugins directory)?  Or have you removed that, and are
using Oracle/Apple's Java Plugin2?

Can you also reproduce with FF 3.6.13?  Or 3.6.12?

Comment 33

6 years ago
You might have to open the applet page a 2nd time after leaving. Here applets work fine with a fresh started Firefox.

Comment 34

6 years ago
I am using plugin2.   I had removed the bundled plugin prior to 3.6.14 being installed.   At this point, I have reverted back to 3.6.13 and everything works fine again.

Updated

6 years ago
Duplicate of this bug: 638499

Comment 36

6 years ago
(In reply to comment #25)
> I can't reproduce this bug using the steps-to-reproduce from comment
> #0.  I tested with FF 3.6.14 on Windows XP (fully patched) with the
> latest Java 6 from Oracle (v6u24).
> 
> Anyone else able to reproduce this on Windows XP?

Yes, I can replicate it on a fully-patched Windows XP with the latest Sun/Oracle Java plug-in, using the steps from Comment 0. I previously replicated it with Plug-in v6u20. The trigger is clearly Firefox 3.6.14, not a specific JRE or Windows version.

As you can see below, the URL is *not* malformed. It *is* relative, which is valid as far as I know. Relative URLs should be resolved relative to the codebase of the applet; the default codebase if not specified is the document codebase (as you would expect).

From the console:

Java Plug-in 1.6.0_24
Using JRE version 1.6.0_24-b07 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\tjc
----------------------------------------------------
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
o:   trigger logging
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
x:   clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------


Your Java configuration is as follows:<br/> <br/>Vendor: <b><a href="http://java.com">Sun Microsystems Inc.</a></b><br/>Version: <b>Java SE 6 Update 24</b><br/>Operating System: <b>Windows XP 5.1</b><br/>Architecture:  <b>x86</b>
Obj:1.6.0_24
Exit worker loop
exception: Permission denied: null.
java.lang.SecurityException: Permission denied: null
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Exception: java.lang.SecurityException: Permission denied: null
java.net.MalformedURLException: no protocol: TestVM2-test.jar
	at java.net.URL.<init>(Unknown Source)
	at java.net.URL.<init>(Unknown Source)
	at sun.plugin.util.GrayBoxPainter.setProgressFilter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.setupGrayBoxPainter(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.showAppletException(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
We don't need any more reports that some people can reproduce this bug -- that's been clearly established.

What I need to find is precise enough steps-to-reproduce that I myself can reproduce this bug.  I'm working on that, and am making progress.

Comment 38

6 years ago
Just tested the (German) 3.6.15 build1 candidate from ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.15-candidates/build1/unsigned/win32/de/ and still have the same issue with it as in 3.6.14

STR:
- open http://www.java.com/de/download/help/testvm.xml
- page loads with an java applet telling if you use current plugin or not
- change to i.e. www.google.com on the same tab
- again open http://www.java.com/de/download/help/testvm.xml (either by entering address or simply going back to last page)
- now the java applet shows only ~40% topmost content, remaining rectangle is filled grey
- reloading with F5 or Ctrl-F5 reloads page but plugin area remains broken
- opening a second firefox doesn't help, here the plugin is broken on the first try
- only closing all firefox instances and starting a new one allows the plugin to work again, but only once

The java test page is the German one, strangely it doesn't happen with the English one: http://www.java.com/en/download/testjava.jsp

Screenshots, first try left, second try right:
http://www.harald-langhammer.de/javabug.gif

Comment 39

6 years ago
This should be a Firefox 4.0 blocker.
> This should be a Firefox 4.0 blocker.

Are you saying you can reproduce this with an FF4 beta or nightly?
(In reply to comment #38)

> Just tested the (German) 3.6.15 build1 candidate from
> ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.15-candidates/build1/unsigned/win32/de/
> and still have the same issue with it as in 3.6.14

Interesting.  As far as I know, that build doesn't have my patches for
bug 611910 or bug 620773 (which are supposed to have caused/triggered
this bug).

Am I right, Chris?

Comment 42

6 years ago
(In reply to comment #40)
> Are you saying you can reproduce this with an FF4 beta or nightly?

Sorry, I should have been more explicit: I saw the problem described in comment 38 (bottom half of applet gray) with the latest nightly build of Firefox 4. It doesn't happen every time.

Mozilla/5.0 (Windows NT 5.2; WOW64; rv:2.0b13pre) Gecko/20110303 Firefox/4.0b13pre
Windows XP
Java 6 Update 23
(In further reply to comment #38)

Bingo!

Your steps-to-reproduce work for me -- and (very interestingly) only
with the German site
(http://www.java.com/de/download/help/testvm.xml), not with the
English language one (http://www.java.com/en/download/testjava.jsp).

Thank you, Harald!

I've no idea why I'm only able to see the bug with the German site.
And I'm not sure how significant that is (as others can apparently
reproduce the bug with the English site).

But having easy STR is more than half the battle.  Presuming they stay
easy to reproduce, I'll report my regression ranges shortly.

Updated

6 years ago
Duplicate of this bug: 638530

Comment 45

6 years ago
(In reply to comment #17)
> We have an increasing number of Firefox users that cannot log on to our online
> banking due to the FF 3.6.14 / JRE error.
> 
> Since this potentially affects 1,000,000+ eBanking users, some help would be
> greatly appreciated...
> 
> Java console:
> **************************************
> 
> exception: Permission denied:
> https://ebanking.sampopankki.fi/html/java/GWPKI/SAM/.
> java.lang.SecurityException: Permission denied:
> https://ebanking.sampopankki.fi/html/java/GWPKI/SAM/
>     at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown
> Source)
>     at java.lang.Thread.run(Unknown Source)
> Exception: java.lang.SecurityException: Permission denied:
> https://ebanking.sampopankki.fi/html/java/GWPKI/SAM/
> 
> **************************************

Just for the record, I cannot reproduce the issue in FF 4.0 Beta 12.
(Following up comment #43)

I forgot to mention that I've been testing with the en-US version of
Firefox 3.6.14.  (And, as I already mentioned above, I'm testing on
Windows XP with the latest Java -- Java 6 Update 24.)

Updated

6 years ago
Duplicate of this bug: 638541

Updated

6 years ago
Duplicate of this bug: 638583
Created attachment 516708 [details]
German testvm.xml Java error

(Following up comment #43)

Harald's testcase (http://www.java.com/de/download/help/testvm.xml)
turns out to be unusual, and therefore not the best testcase for this
bug.  But I've since found a couple other testcases that "work" (for
me) more like what others have reported here, and which will help me
decipher this bug (I'll discuss them in my next comment).

The German testvm.xml site fails using Harald's STR from comment #38
(on the 1.9.2 branch, when my patch for bug 611910 is present) with
the errors that others have reported here.  But reloading that site
fails with different errors when my patch for bug 611910 isn't present
on the 1.9.2 branch, on the trunk (whether or not my patch for bug
611910 is present), and even in IE8!

This explains Harald's problems with the 3.6.15 candidate build, and
shows that the problem he reported in comment #38 is either unrelated,
or not very closely related.
Created attachment 516711 [details]
Colorpicker Java error

Two new testcase sites:

http://www.lohn1.de/lobn.htm
http://navsurf.com/applets/colorpicker/

Reloading these sites fails on the 1.9.2 branch (FF 3.6.X), when my
patch for bug 611910 is present, with at least some of the errors that
others have reported here.  F5 and the reload button both "work".

In my tests I only need reload the first site once.  I sometimes need
to reload the second site two or three times.

I will try to create a reduced testcase that shows exactly what's
going on here ... but that will probably take a while.

I don't know why these sites don't fail to reload on the trunk (what
will become FF4) -- even with my patch for bug 611910 present.  But I
aim to find out.

The first 1.9.2-branch nightly in which these problems occur is the
firefox-2011-11-23-04-mozilla-1.9.2 nightly -- the one where my patch
for bug 611910 first landed.

Comment 51

6 years ago
I found the problem guys! It took me upgrading to 4b13 to realize this though LOL. There seems to be an issue with ADBLOCK PLUS that is doing this. I disabled ALL Adblock stuff, and things are working again.

If you guys aren't using Adblock - try going into safe mode - with all the add-on's disabled, and see if that solves it.

And, then if that doesn't solve the issue....you can always try unintalling Java (cause, it seems to leave leftovers from every update in there) and re-installing. The BEST way to do this is with a program called REVO Uninstaller. It gets rid of ALL traces of Java - and, then you can do a clean install!

Hope this helps! :)

Comment 52

6 years ago
The VM I reproduced it with didn't have adblock plus installed...
> There seems to be an issue with ADBLOCK PLUS that is doing this.

Running Adblock Plus may make it easier to reproduce this bug, but it isn't the cause.

I'm not using Adblock Plus, and I can reproduce this bug using the sites from comment #50.

> Hope this helps! :)

It does -- it might explain why I've had such a hard time reproducing this.

Comment 54

6 years ago
In case it helps you repro... This page will fail after the 3rd refresh:
http://www.screencast-o-matic.com/detect-full-url.html

After the 3rd refresh the getDocumentBase() function on the applet returns null and you can no longer call functions on the applet via javascript.

Here's a screencast showing the failure:
http://www.screencast-o-matic.com/watch/cXee0w2Xb

Also here's another page which uses a relative path to the jar which also fails on the 3rd load but the error in the console is different:
http://www.screencast-o-matic.com/detect.html
For what it's worth, I (like Andy Pople) can also reproduce this bug
on OS X (10.5.8 and 10.6.6) with FF 3.6.14 -- though (of course) only
when using Java Plugin2 (not when using the JEP that's by default
bundled with FF 3.X on the Mac).

See comment #30, comment #32 and comment #34.

Updated

6 years ago

Comment 56

6 years ago
I can reproduce the bug with Ubuntu Linux 10.4 LTS too. Firefox is installed and updated via Ubuntu repository.

Updated

6 years ago
Duplicate of this bug: 638536

Comment 58

6 years ago
This issue dissatisfies many 3.6.14 users in the support forum.
A dedicated KB article has been created: https://support.mozilla.com/kb/pogo-and-other-java-pages-dont-work.
I marked is as blocking for 3.6.15.

It could be a regression from bug 570249 or bug 478823.
blocking1.9.2: --- → ?
Component: Extension Compatibility → Plug-ins
Product: Firefox → Core
QA Contact: extension.compatibility → plugins
Version: 3.6 Branch → 1.9.2 Branch

Comment 59

6 years ago
Why this error still occurs?
We have financial customers using applets and now Firefox have automatic updated to this 3.6.14 and all is broken!

ASAP fix for this is needed.

plugin2manager.parentwindowDispose
PluginMain: JNLP2Manager creation: java.net.MalformedURLException
java.net.MalformedURLException
    at java.net.URL.<init>(Unknown Source)
    at java.net.URL.<init>(Unknown Source)
    at java.net.URL.<init>(Unknown Source)
    at sun.plugin2.main.client.PluginMain.handleMessageStartApplet(Unknown Source)
    at sun.plugin2.main.client.PluginMain.mainLoop(Unknown Source)
    at sun.plugin2.main.client.PluginMain.run(Unknown Source)
    at sun.plugin2.main.client.PluginMain.main(Unknown Source)
Caused by: java.lang.NullPointerException
(In reply to comment #50)

> It could be a regression from bug 570249 or bug 478823.

It's clearly a regression from my patch for bug 611910.  Though it's a
complex bug, and I'm sure other factors are involved.  See comment
#50.

Why do you mention those two bugs in particular?

Comment 61

6 years ago
I haven't seen bug 611910 in the release notes of 3.6.14, but its 1.9.2 status has been changed yesterday.
The two bugs I mentioned are the only plugins bugs I saw in the release notes of 3.6.14.
> The two bugs I mentioned are the only plugins bugs I saw in the
> release notes of 3.6.14.

Oh, OK.  So we can safely say they aren't relevant here :-)

If you have the time, it's of course best to get a nightly regression
range.

> I haven't seen bug 611910 in the release notes of 3.6.14, but its
> 1.9.2 status has been changed yesterday.

I don't think all bug fixes make it into the release notes.  And bug
611910 was initially labeled a security bug -- which might have
prevented its inclusion.

Comment 63

6 years ago
We're fixing this by backing out 611910. This bug is staying open for investigation as the patch also landed on trunk (even though we haven't been able to reproduce there).
blocking1.9.2: ? → .15+
status1.9.2: --- → .15-fixed

Updated

6 years ago
Blocks: 611910
The "3.6.15" we're releasing today does not fix this bug, the release containing this bug fix has been renamed to "3.6.16" and the bugzilla flags will be updated to reflect that soon. Today's release is a re-release of 3.6.14 plus a fix for a bug that prevented many Java applets from starting up.

Comment 65

6 years ago
(In reply to comment #64)
> The "3.6.15" we're releasing today does not fix this bug...
> Today's release is a re-release of 3.6.14
> plus a fix for a bug that prevented many Java applets from starting up.

A _different_ bug that prevented Java applets from starting up? Because this one does too (fairly dramatically)...

Comment 66

6 years ago
@Daniel Veditz(In reply to comment #64)
> The "3.6.15" we're releasing today does not fix this bug, the release
> containing this bug fix has been renamed to "3.6.16" and the bugzilla flags
> will be updated to reflect that soon. 

With "this, do you mean 629030?

> Today's release is a re-release of 3.6.14
> plus a fix for a bug that prevented many Java applets from starting up.

Which exact bug id are you refering to here?

 The confusion is growing...

Comment 67

6 years ago
That was a mass modify, sorry for the confusion.

This bug is indeed the one fixed in 3.6.15 by backing out bug 611910.

If you see this in 3.6.15 still, I want to know (but I'm pretty confident you won't).
Ignore comment 64, this is the bug we're fixing in 3.6.15 -- forgot to take it out of the list of bugs to spam.
Duplicate of this bug: 638810
Duplicate of this bug: 638747
Duplicate of this bug: 638382
Candidate builds for FF 3.6.15 are available at
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.15-candidates/.
Those who see this bug should try them out.

Note that one apparent problem with these builds, reported above,
turns out to be a different issue (one that also happens in IE8).  See
comment #38 and comment #49.

Comment 73

6 years ago
Tested our implementation with 3.6.15 and looks that it fix problems

Comment 74

6 years ago
Firefox 3.6.15 is released now and available from mozilla.com.
Duplicate of this bug: 638877
Duplicate of this bug: 638114

Updated

6 years ago
No longer blocks: 638114, 638382

Updated

6 years ago
No longer blocks: 638070
Duplicate of this bug: 638070

Updated

6 years ago
Duplicate of this bug: 638919
I've found the *real* cause of this bug -- it's a bug in how plugins
are started and stopped.

So there's nothing wrong with the concept of a scheme whitelist for
Java, or (basically) with how my patches for bug 611910 and bug 620773
implemented it.  Or if there *is* something wrong with the concept of
a Java scheme whitelist (or with my implementation of it), this bug
doesn't demonstrate it.

I haven't yet worked out the details of the
plugin-starting-and-stopping bug, or found out when it started
happening (or if it still happens on the trunk).  That will be at
least several days' work -- which I'll start next week.  I'll open a
new bug on it.

I don't normally announce that I've found a bug before working out the
details.  But some of us (including myself) have been anxious about
the possibility that using a Java scheme whitelist will cause trouble
on the trunk (which still has my patch for bug 611910).  So I just
wanted to relieve that anxiety.

For the curious:  Break on NS_CheckIsJavaCompatibleURLString() and try
to reproduce this bug.  You'll find that it only gets called once
(when the applet is first loaded, successfully), and that it never
indicates that any urlString is incompatible.
Duplicate of this bug: 638808

Comment 81

6 years ago
I seem to have a general problem with java-scripts since 3.6.14. I am now running 3.6.15 and it is still a problem. Facebook is not usable anymore. And many more sites I regularly use. I does work if I start Firefox in safe-mode. I have not yet tried to go back to 3.6.13. But I am sure it stopped working in 3.6.14. You think this is related??

Comment 82

6 years ago
(In reply to comment #81)
> I seem to have a general problem with java-scripts since 3.6.14.
> [snip]
> You think this is related??

If the problem is really with *JavaScript*, then no -- Java and JavaScript are unrelated technologies (just with similar names). This bug relates to Java applets, not JavaScript.

Comment 83

6 years ago
Sorry to disturb. It was just that this was the only bug I found remotely like I was feeling Firefox behaving, except it was javascript. Now after a second round of disabling plugins one by one I think I have found the plugin causing this.
I've opened bug 639647 ("Restore Java scheme whitelist for NPRuntime plugins on the 1.9.2 branch").
I've got a patch (and a test build) at bug 639647 comment #1 that
fixes the underlying cause of this bug (instead of just backing out my
patches for bug 611910 and bug 620773).

Please test it out, and let us know your results (preferrably at bug
639647).

Comment 86

6 years ago
Will you let us know when this is fixed.  Mozilla keeps asking me to update and I have to say "later".  Thank you.

Comment 87

6 years ago
Re Comment #86: You don't have to wait. In terms of the released versions, the bug only existed in 3.6.14. The current version is 3.6.15, which was released specifically to address this problem (by temporarily backing out the other change that caused it). So you can safely update Firefox right now.
While you're at it, please also try out the test build I mentioned in comment #85 (download and install it separately).  It should also fix the problem(s).

I need other testers besides myself :-)

Comment 89

6 years ago
Thank you so much for addressing this problem.  I have now updated to 3.6.15.  Good going guys!  About the test thing; I don't think I'm really all that computer literate so I'll save myself some worry by passing this up.  Thanks again.

Comment 90

6 years ago
Why isn't this resolved FIXED?
> Why isn't this resolved FIXED?

It seems we forgot to.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Comment 92

6 years ago
Steve: Can you please have a look at bug 675642? I believe the fix to this problem has possibly caused inline pdfs to randomly not load.
I don't have time to do it now.  With luck I'll have time next week.

Comment 94

6 years ago
Steve: I apologize but from what my users have experienced, and they are able to do more extensive testing than I can, it appears this fix did not cause a regression with inline PDF's.

I would however greatly appreciate a gander at bug 675642, as its been open for months without any resolve and is becoming a big issue for our organization.

Thanks,
  Tyler
You need to log in before you can comment on or make changes to this bug.