604492 - Investigate java compatibility with ipc on osx

Status: RESOLVED WORKSFORME

(Core Graveyard :: Plug-ins, defect)

Description

[Jim Mathies [:jimm]]

On windows we are disabling oopp for java plugins (bug 603417) due to conflicts between our ipc model and sun's process isolation model (bug 555699). This raised the question of whether or not sun/apple implementations have conflicts as well on macs.

We need to confirm java is operating correctly and look for issues in our ipc event model that might conflict with whatever sun/apple have implemented.

Comment 1

[Benjamin Smedberg]

Can somebody with a mac OOPP please visit http://www.dragmath.bham.ac.uk/demo.html and let us know if it crashes 60 seconds after the signature dialog shows up?

Comment 2

[Steven Michaud [:smichaud] (Retired)]

The Java Plugin2 security dialog behaves differently on OS X than it
does on Windows.  So bug 555699 doesn't happen on OS X.

But similar problems do happen, which (though not as serious) are at
least somewhat disturbing.  They happen whether or not OOPP is on for
Java Plugin2, and on both OS X 10.6.4 and 10.5.8.

The Java Plugin2 security dialog isn't modal on OS X.  This means
that, while it's displayed, you can still interact with Minefield's
menus and the browser window.  You can even close the window or tab
the dialog was displayed from!  This (after several additional steps)
can cause the Java child process to crash (whether or not Minefield is
using OOPP).

But the worst effect I've been able to discover is what happens when
you start feeding a lot of mouse events to the window/tab from which
the security dialog was launched, without closing the dialog (I found
this easiest to do with the mouse's scroll wheel).  After a certain
threshold, the browser appears to freeze -- it beachballs.  But the
"freeze" disappears if you dismiss the security dialog (whether you
allow or deny the applet access to your computer).

I'll open one or more bugs on these issues as and when I have time.

Disabling OOPP for Java Plugin2 on OS X won't fix any of these
problems, so I consider this bug closed.  But I don't how to close it
-- WORKSFORME?

Comment 3

[Steven Michaud [:smichaud] (Retired)]

Josh agrees we should close this WORKSFORME.