New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JVM crash on GC with current maven snapshot #420
Comments
I could try on another machine (linux 64bits, xubuntu 12.10) and it does not crash on GC.
The used GPU is a secondary card (not used for any display). |
Hi @twitwi , Thank you so much for investigating and providing such a narrowed down test case! Also, have you made sure the exact same version of Java is being used on both setups? (and have you tried turning compressed oops on/off, just in case?) Could you also try calling Finally, a fuller native stack trace might be useful, please do not fear of spamming this issue with a larger log :-) Cheers |
I tried (on the failing machine) with two versions of java (6 and 7), varying UseCompressedOops and bridj.protected.
Results incoming… |
Overall, with optirun, the only impacting variable is the javacl-core version (RC3 (works) vs SNAPSHOT). Overall, with amdapp (cpu, no ati card), bridj.protected=true makes the CL platform not found, while RC3 works and SNAPSHOT does the same error. The java version, UseCompressedOops and releasing the context seem to have no impact. Details: Script that produced it:
Maybe, I should bisect the thing if it is not reproducible elsewhere. |
I just read part of the JavaCL code and I have a note to add. My AMDAPP is not installed in /opt/AMDAPP/lib (custom install)… in case it matters |
Hi @twitwi , Thanks for taking the time to investigate, much appreciated! I'm now trying to install mint linux :-) Cheers |
Just to check: are you using the Ubuntu-based Linux Mint (the default one), or Linux Mint Debian Edition? |
default one |
(ubuntu based, not kubuntu neither) |
Hi @twitwi , Could you please try again with the latest 1.0-SNAPSHOT? There's a magic one-line fix that might help... Cheers |
Hi and thanks for the patch, |
Hi Rémi, Friendly ping :-) Cheers |
I seem to be seeing the same error with RC3: When garbage collector runs, there is an Access Violation error due to CLDevice cleanup (log attached with stack trace etc.) Using JavaCL 1.0.0-RC3 Environment: Windows 8.1, two OpenCL platforms To replicate (simple Scala app):
Same problem when calling JavaCL.getBestDevice() Getting the CPU devices, on the other hand works ok:
Relevant part of the log dump:
|
This issue was moved to nativelibs4java/JavaCL#18 |
Hi @ochafik
I have a (now) very simple program that crashes with the latest maven snapshots but works with javacl-1.0.0-RC3.jar.
I run using optirun under linux mint 15, 64bits, with a "NVS 5400M (NVIDIA CUDA)" device. The rest of the program works fine (complicated opencl kernel work) but the GC crashes the VM with:
It might be a temporary issue (or specific to my device) but I prefer to report it.
Rémi
The text was updated successfully, but these errors were encountered: