Closed Bug 1006499 Opened 10 years ago Closed 10 years ago

Java applet crash when file chooser is open and idle

Categories

(Core Graveyard :: Plug-ins, defect)

29 Branch
x86_64
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: venubwal, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140421221237

Steps to reproduce:

MAC OS 10.6: open Firefox 25,28,28
open applet that has FileChooser which appletOpenDialog() to allow user to select files
just select files BUT DO NOT submit Dialog
keep idle for 1 mins
you see fire fox crash
-------same scenarios works file with Safari/crome...
similar issue is not exists in windows----but sometime after 10 mins idle



Actual results:

firefox crash on applet (file chooser) open for 1 minute


Expected results:

I found related issue, but not exact one.
Bug 700835 - [Mac] Firefox 8 and up crash with Apple's latest Java updates for OS X 10.6 and 10.7 closing tab/window containing Java applet
I found error at MAC Console when this happens
------------
pm java[1087]: java.lang.NullPointerException
	at sun.awt.SunToolkit.getSystemEventQueueImplPP(SunToolkit.java:1003)
	at sun.awt.SunToolkit.getSystemEventQueueImplPP(SunToolkit.java:998)
	at sun.awt.SunToolkit.getSystemEventQueueImpl(Sun
------------------
But, Issue as-well above error not appears on fire fox 17
Severity: normal → critical
OS: Windows 7 → Mac OS X
I would expect us to kill off the Java plugin because it is blocking the browser with its modal dialog and nested event loop. All dialogs should be asynchronous with respect to the NPAPI.

All of Firefox crashes, or just the Java plugin crashes? Do you see the Firefox crash reporter? Do you have a URL or testcase that can be used to reproduce this?
Group: core-security
Component: Untriaged → Plug-ins
Flags: needinfo?(venubwal)
Product: Firefox → Core
Here are the crash reports
---------------------------
Report ID 	Date Submitted
065E88A9-C331-4815-879F-1486EC3DA121	06/05/14	5:23 pm
2FEADE63-D968-4F2A-88AC-F0EF390C722E	02/05/14	6:09 pm
2EFD6E9F-C7CF-422C-B9A8-703493A06D9C	02/05/14	5:51 pm
4490E2AD-35C8-46CB-A42A-03E865489FD9	02/05/14	5:49 pm
------------------------------
Here we User Flex ExternalInterface.call("appletOpenDialog", hidden, restricted, singleSelect, i18nMessages); And as per below links these are linked and supported only from single thread call.
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/external/ExternalInterface.html
https://developer.mozilla.org/en-US/Add-ons/Plugins/Gecko_Plugin_API_Reference/Scripting_plugins
(Threading model)
->But, I am not sure how come we can make 'asynchronous' upon those standards.
->** ExternalInterface call will handled by JSP where applet object will be invoked where it has JFileChooser to select files from dialogue. *** A another call will be handled to collect all such selected files!
-------
How come we can kill java plugins behind the user interaction. In general it gets kill once user close dialogue after selection automatically. This is a typical scenario where after 1 min firefox crash IF-F dialogue is IDLE
....
Flags: needinfo?(venubwal)
Those crash reports were never actually submitted. You could click the link to submit them and then paste the server crash ID, which should start with "bp-". But given the extra information, I think I see what's going on.

The prior comments were about the Java plugin, but comment 3 is talking about actionscript/Flash APIs. It seems that you are using both Flash and Java?

The basic problem here appears to be that you're using JFileChooser, which shows a modal dialog on the main applet thread and blocks the browser. You should either stop using JFileChooser, or move it to another thread and use asynchronous callbacks to avoid blocking the browser.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.