| Summary: | java.awt.Desktop performance drops after JOGL initialization | ||
|---|---|---|---|
| Product: | [JogAmp] Jogl | Reporter: | trnecka_david |
| Component: | windows | Assignee: | Sven Gothel <sgothel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | --- | ||
| Version: | 2 | ||
| Hardware: | pc_x86_32 | ||
| OS: | windows | ||
| Type: | --- | SCM Refs: |
jogl f2bd50ff25009de477a203460abe8a5597acdbc5
|
| Workaround: | --- | ||
| Attachments: | Minimal repro case | ||
There are still WinXP machines out there ? Hmm .. if possible, pls re-test w/ latest sources, or upcoming aggregated autobuild. Added unit test in commit f2bd50ff25009de477a203460abe8a5597acdbc5. (Will push it soon) Will close this bug unless it persist in your configuration, please retest. |
Created attachment 366 [details] Minimal repro case The first invocation of java.awt.Desktop.open() done after the JOGL is initialized by a GLProfile.initSingleton() blocks execution for about 30 seconds. Any subsequent call to the Desktop API works as expected, with no delay. Reproduced on Windows XP SP3 x86, JRE 1.7.0_05, JOGL2 rc10. Does not happen with Windows 7 x64. Traced Desktop.open() down to native, the problematic call is the ShellExecute windows API. Repro case attached.