X crashes when terminating java3d application....

Question

I have an application which uses java3d. So we've tried to bundle java3d with the application. Everything runs fine till the application is terminated, when X crashes.
* Added j3audio.jar, j3utils.jar, j3core.jar and vecmath.jar to JAVA_HOME/jre/lib/ext
* Added libJ3D.so, libJ3DUtils.so and libj3daudio.so to JAVA_HOME/lib/i386
What might be the problem?
Rana

Answer 1

Wow. I thought I was the only person in the world with that problem.
I had not played with Java3D for many months (mostly because of stated problem). Last week, I
loaded up the latest Java3D (I think I got it from Blackdown). I verified that problem still exists. I then
proceeded to play with the old NCSA Portfolio object file loader. When I exited the sample program,
my X DID NOT DIE!
After that, I ran my other 3D programs and they no longer crashed either.
Doesn't make much sense. I checked the exit code for the Portfolio sample program, and it just does
a System.exit(). I don't see how it could be that program, but nothing else changed. Maybe something
was cached in some 3D RAM somewhere, or maybe the new Java3D fixed it and there's some other
reason why the fix didn't happen right away. Definitely needs more testing (most importantly, to see
whether the problem is permanently fixed or was just fixed for that X session). Since my desktops are
filled with work, I can't hazard running a 3D app to test it now.
SYSTEM SETUP DETAILS FROM LAST YEAR
Same problem happened consistently on 4 Linux workstations that were running RedHat 6.2, then
7.0, then 7.1 (the problem did not change over OS upgrades). I used generic RH kernels and
kernels built specifically for the corresponding graphic chipsets and DRI support-- didn't matter at
all.
If you find out anything, pls update this thread. I will update it this eve if I have time to do more testing.