Posted by notzed on Aug 28, 2010; 4:43am
URL: https://forum.jogamp.org/Re-segfaults-working-version-tp911744p1379033.html

Merijn Vogel wrote

The installed driver seemed to be 256.40, it's now 256.44.
That 195.something source was apparently old. For me it was 2am last night that I asked you, so thanks for the tip and I'll keep trying.

It's still unstable, I'll try to create an isolated algorithm that misbehaves soon, so someone who likes to help can point out the "obvious" mistake I make.

I tell you what, the Nvidia stuff is shit, don't believe the hype about how their 'software is so much better'.

I managed to get a relatively stable setup using the beta driver (258.19) but to be honest it's still not fantastic.  I'm simulating processing 'real time' video using a throttled feed from disk and if I turn off the throttle it generally crashes within seconds.  The crappy profiling tool crashes even with the delayed processing (on microsoft's system as well).  I think it's just luck that the app is stable at this point - which I don't feel too comfortable about as I continue to develop it.  It was relatively stable with an older driver too (even with the jvm interaction bug and lots of bugs in my jocl side code) until I added some more processing.

Although I think i'm doing things right (especially wrt threading) I wouldn't put it past a bug in my code either, but you really just can't tell from the instant-death-segfault in the jvm what's going on.