Bug 1301

Summary:	OpenGL profile init takes up to one minute ( win 10 + nvidia 7xx )
Product:	[JogAmp] Jogl	Reporter:	Maxime Caignart <maxime-jogamp>
Component:	core	Assignee:	Sven Gothel <sgothel>
Status:	RESOLVED INVALID
Severity:	normal	CC:	gouessej, john.mckisson, sgothel
Priority:	P4
Version:	2.4.0
Hardware:	pc_x86_64
OS:	windows
Type:	DEFECT	SCM Refs:
Workaround:	---
Attachments:	jogamp console logs log amd+win7

Description Maxime Caignart 2016-04-11 19:20:02 CEST

Hello,

I've got multiple users of my game that experience a very long openGL init on their machines.
It can take up to one minute of time, leading players to think that the game is just no working.
The common ground of this issue is Windows 10 + nVidia card ( more specifically 7xx ).


Nothing fancy is done for the GlProfile init. 

GLProfile glProfile = GLProfile.get(GLProfile.GL2);

I requested logs with -Djogamp.debug=ALL but the result is not showing anything special.

Comment 1 Julien Gouesse 2016-04-12 10:20:08 CEST

Hi

Please can you be more accurate on their hardware and the version numbers of their drivers? Do they use laptops? Optimus? I can try to reproduce this bug. Is it reproducible with Quadro graphics cards too?

Comment 2 Maxime Caignart 2016-04-12 10:47:02 CEST

Created attachment 779 [details]
jogamp console logs

console logs of the game launched with -Djogamp-debug=all

Comment 3 Maxime Caignart 2016-04-12 16:09:42 CEST

People having this issues are using Windows 10  with geforce 7xx, up-to-date drivers, no Optimus, desktop computers.

I can't tell much more now, but some of them are willing to help.

Comment 4 John McKisson 2016-06-11 19:26:59 CEST

Hello

This is also happening on my machine, Windows 10 Pro 64 bit, Nvidia 780Ti, latest drivers...

It seems like the call to GLProfile.initSingleton() is consistently taking ~60.xx seconds to execute.

Some background:  I was initially experimenting with Ardor3D (.9?), which was working flawlessly with no initialization delay.  However the newer version of jogl used by JogAmp Ardor3D Continuation does have this problem.

I'm pretty sure that I am capable enough to get jogl built from source and run some tests for you if need be.

Comment 5 Julien Gouesse 2016-06-11 19:36:14 CEST

Thanks, I'll find which version of JOGL the old obsolete Ardor3D 0.9 uses. JogAmp's Ardor3D Continuation uses JOGL 2.3.2.

Comment 6 John McKisson 2016-06-12 19:44:28 CEST

I've narrowed it down a bit, looks like what I am experiencing is not the same as Maxime, rather it seems to be a timeout in IOUtil.testDirExec...

I will submit a separate bug report with console log.

Comment 7 Julien Gouesse 2016-06-12 19:56:23 CEST

(In reply to John McKisson from comment #6)
> I've narrowed it down a bit, looks like what I am experiencing is not the
> same as Maxime, rather it seems to be a timeout in IOUtil.testDirExec...
> 
> I will submit a separate bug report with console log.

The workaround consists in disabling the automated native library loading and using the Java library path wisely.

Comment 8 Maxime Caignart 2016-10-06 13:47:47 CEST

Created attachment 792 [details]
log amd+win7

Here's a log of the similar startup time issue.

This happens not only with the nvidia + win10 combo as this log is about AMD FirePro V4800.

The whole GL init time, triggered by GLProfile.get(GLProfile.GL2); is taking 50 seconds.

Comment 9 Maxime Caignart 2016-10-06 13:49:39 CEST

I've added an extra comment line ">>>> VERY LONG TIME <<<<" in the logs to show where the system is freezing for a long time

Comment 10 Maxime Caignart 2016-11-03 11:01:06 CET

I've managed to solve the issue using the parameter :  -Djogamp.gluegen.UseTempJarCache=false and taking care of providing the natives.

Comment 11 Sven Gothel 2019-03-30 04:07:50 CET

Comment 10 indicates that using TempJarCache causes issues on the reporter's machine, which might be due to some 'security tools' or the TEMP folder is as slow?

Marking this bug as invalid.