Crash

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Crash

tich
Hi,

I have an application based on WorldWind (and so on JOGL 1.1) which crashes several hours even if there is only few objects displayed. I have tried it with the following configurations (obtained from glxinfo) running on RHEL5.2 :

1) OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: GeForce 8400 GS/PCI/SSE2
    OpenGL version string: 3.0.0 NVIDIA 185.18.14

2) OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: Quadro FX 1800/PCI/SSE2
    OpenGL version string: 3.0.0 NVIDIA 185.18.14

3) OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: Quadro FX 1700/PCI/SSE2
    OpenGL version string: 3.0.0 NVIDIA 185.18.14

4) OpenGL vendor string: NVIDIA Corporation
    OpenGL renderer string: Quadro FX 1800/PCI/SSE2
    OpenGL version string: 3.0.0 NVIDIA 185.18.14

I do not understand where the problem (see several hss_err_pid log files in attachemebt). I saw some post on the Internet on potential JVM bugs, memory leaks with NVidia drivers, bug in thread optimization, problem with TextRender ... but I don't where to start.
Perharps someone has already seen this problem before ?
Can somebody help me to start to investigate, please ?

hs_err_logs.zip
Reply | Threaded
Open this post in threaded view
|

Re: Crash

gouessej
Administrator
Hi!

I identify several root causes. You get a crash even on some very basic OpenGL calls (glVertex3d, glTexImage2D) and when using the picking in WorldWind. At first, tell me exactly which graphics card you use and please install the most appropriate driver. Then, try to reproduce your bug anew, it will help you to focus on real bugs rather than wasting some time with a driver that should not be used with your hardware.

I have a more recent NVIDIA Quadro FX at work under Cent OS 5.3 and it works fine.

Best regards.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: Crash

tich
Hi, I've finally found a memory leak in my code. It seems to work fine now.