Login  Register

Re: Mac OS X 10.8 + Java 7 Poor Animation and Lockups

Posted by Sven Gothel on Jan 07, 2013; 12:38am
URL: https://forum.jogamp.org/Mac-OS-X-10-8-Java-7-Poor-Animation-and-Lockups-tp4027723p4027724.html

On 01/07/2013 01:27 AM, Gene [via jogamp] wrote:

> Hi guys.  Major problem:
>
> Have a JOGL app that runs great with the last Apple JRE 6 and breaks with
> newest Oracle JRE 7.  Tried both  rc11 and rc10 of JOGL.  
>
> Symptom is that a GLCanvas animation in the Swing app refreshes only about 4
> frames per second even though the app says it's rendering at 38.  Then when
> the animation is turned off with the GUI, which causes
> GLCanvas.setVisible(false) internally, GUI hangs, though no exception is raised.
>
> MacBook Pro, 15-inch, Late 2008
> 2.8 GHz Intel Core 2 Duo
> OS X 10.8.2 (12C60)
> NVIDIA GeForce 9400M 256 MB
>
> This is a major production problem for an app with many thousands of users.
> For the time being I will either have to bundle it with JRE 6, which triples
> the download package size, or junk the JOGL animation feature which will make
> many people unhappy.
>
> Before I try to cook up a small example for a bug report, is this a known
> issue?  Workaround?
Unknown issue.

>
> I am guessing maybe Oracle had to use the OpenGL rendering pipeline for Java
> 2D because Apple didn't give them the one for Quartz, and this is conflicting
> with JOGL?  
Not w/ GLCanvas and Java7 where we use an offscreen layered code path
not the instable GLJPanel shared-Java2D-FBO patch. (Note: The latter is
disabled per default.)

> I can find zero info on the web about how Oracle Java 7 is
> rendering Java 2D on Mac OS X.
I don't think this is the issue.

>
> Thanks for your help.  I'm really against the wall with a ship date 9 days
> from now.

Well, I would appreciate your unit test.

Please do the following:
  - Use our Bugzilla and create a new bug entry
    w/ the most detailed description

  - Create a minimal unit test (best if it's a modified one of ours,
    but any which reproduces the code (w/o fuss) will do.

  - Attach the unit test to your bug report (java file, git patch, ..)

  - Maybe even add a git pull request (optional)

~Sven



signature.asc (909 bytes) Download Attachment