OOP java Plugin Causes Firefox to hang

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
8 years ago
6 years ago

People

(Reporter: rakshithbekal, Unassigned)

Tracking

Trunk
x86
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: dupeme)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.2a1pre) Gecko/20110408 Firefox/4.2a1pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.2a1pre) Gecko/20110408 Firefox/4.2a1pre

choosing out of process java plugin causes Firefox to hang when java is initiated. I haven't seen any improvements in this case from the day I enabled it. Is anyone fixing it? or atleast largely aware of it?

Reproducible: Always

Steps to Reproduce:
1.enable dom.ipc.plugins.java.enabled in"about:config"
2.run a java test somewhere I test here http://www.intel.com/p/en_US/support/detect/?iid=gg_support-in+home_detect
3.Experience hand before result.



This problem's been there since beta versions to the current nightly.
If I recall correctly OOPP Java has been disabled on Purpose (hence dom.ipc.plugins.java.enabled;false) since the Plugin needs Changes to work flawless with IPP.
Whiteboard: dupeme

Comment 2

8 years ago
(In reply to comment #1)
> If I recall correctly OOPP Java has been disabled on Purpose (hence
> dom.ipc.plugins.java.enabled;false) since the Plugin needs Changes to work
> flawless with IPP.

yep. Java has it's own oop model which conflicts with ours, so we turned ours  off. This bug won't have a shot at getting fixed until we get content processes in about a year or so.
(Reporter)

Comment 3

8 years ago
This is what Oracle had to say about my same bugpost there 

"Thanks for your bug report http://webbugs.us.oracle.com/rt/incidentDisplay?incidentID=2010281

We are treating this as an enhancement request for a future release of Java.  Java already runs user applications in a separate process space from the web browser.  The Java plugin is a small VM+launcher that does run in the browser process space, just to communicate with the client VM and render the user application.  Typically crashes are caused by the actual application, not the plugin itself, so you already have most of the benefit of this Firefox feature, on all browsers on all platforms."

Updated

7 years ago
Version: unspecified → Trunk

Comment 4

6 years ago
I have to enable dom.ipc.plugins.java.enabled to make sure that the java plugin does _not_ get stuck. What is the story here?

Java is 1.6.0-26, Firefox is 13.0 on Debian (amd64).
You need to log in before you can comment on or make changes to this bug.