Posted by Sven Gothel on Jan 26, 2012; 1:15pm
URL: https://forum.jogamp.org/Cross-platform-DLL-selection-tp3667506p3690408.html

On Thursday, January 26, 2012 11:23:27 AM gouessej [via jogamp] wrote:
>
> JOGL 2.0 uses a slightly different path than JOGL 1 during initialization but
> I don't think it's making a more thorough probe of supported features.

We do a more thorough probing w/ JOGL2.

For example, JOGL1 was 'only' creating a context on-demand when a user issues the call.
JOGL2 does query all available profiles and hence it's capabilities.
This query is thorough, ie. it creates the context, makes it current and releases it.

If there is a bug within this query, initialization fails somehow.
We have experienced such failure w/ OS X 10.6 and NVidia, where we had to add
a glFlush() or glFinish() before releasing the context.


> This
> problem mainly occurs under Windows. Could your user provide the full stack
> trace please? It would be very helpful.

Yes, running the 'etc\test_dbg.bat' as our FAQ (Bugreport ..) mentiones
could disclose the root cause of the bug.
    <http://forum.jogamp.org/Problem-with-GLProfile-and-jogl2-rc2-td3447491.html#a3447546>

We actually have a few bug reports in regards Windows XP w/ old driver open,
but since I could not get my hands on those machines and I could not
reproduce the problem with my old machines .. it's hard to find those issues.

> Some applications cannot use a Swing
> rendering path; therefore, fixing this bug is very important in my humble
> opinion.

Of course it is, I agree.
Hope we can get to the root cause.

~Sven