Skip to content
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

SIGSEGV on Ubuntu using JavaCL #405

Closed
tarelli opened this issue May 29, 2013 · 5 comments
Closed

SIGSEGV on Ubuntu using JavaCL #405

tarelli opened this issue May 29, 2013 · 5 comments
Labels

Comments

@tarelli
Copy link

tarelli commented May 29, 2013

This happens either using CPU or GPU device:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=27283, tid=140378190874368
#
# JRE version: 7.0_17-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode linux-amd64     compressed oops)
# Problematic frame:
# C  0x0000000000000000
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping,     try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/mike/geppetto/serviceability/error.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

With stacktrace:

Stack: [0x00007fac58238000,0x00007fac58339000],  sp=0x00007fac58337098,  free     space=1020k
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.nativelibs4java.opencl.library.OpenCLLibrary.clReleaseDevice(J)I+0
j  com.nativelibs4java.opencl.CLDevice.clear()V+7
j  com.nativelibs4java.opencl.CLAbstractEntity.doRelease()V+10
j  com.nativelibs4java.opencl.CLAbstractEntity.finalize()V+1
v  ~StubRoutines::call_stub
J  java.lang.ref.Finalizer.invokeFinalizeMethod(Ljava/lang/Object;)V
J  java.lang.ref.Finalizer.access$100(Ljava/lang/ref/Finalizer;)V
J  java.lang.ref.Finalizer$FinalizerThread.run()V
v  ~StubRoutines::call_stub

The full specs of the system are:

Java:
java version "1.7.0_15"
Java(TM) SE Runtime Environment (build 1.7.0_15-b03)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)

Distro:
Ubuntu 12.04.2 LTS

Kernel:
Linux mike-pdn 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

CPU:
Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz

GPU:
NVIDIA Corporation GT218 [GeForce 310](rev a2)

Full logs:
http://pastebin.com/h2tcbsX7
http://pastebin.com/UiiCDquj

@ochafik
Copy link
Member

ochafik commented May 29, 2013

Hi @tarelli ,

Which version of JavaCL are you using?
This looks like #387, which is fixed in the latest snapshot (I'm long overdue to perform a new release :-S).

Cheers

@tarelli
Copy link
Author

tarelli commented May 29, 2013

Hi @ochafik,
I did try also with SNAPSHOT-1.0.0 back to when you fixed that with no luck, same error. When do you think you are going to be able to release again (would be handy so that I can point to the new version anyway)?
Thanks

ochafik added a commit that referenced this issue Jul 29, 2013
…new -Dbridj.debug.pointer.releases=true). Could be the root cause of #420 and/or #405.
@ochafik
Copy link
Member

ochafik commented Jul 30, 2013

Hi @tarelli ,

Could you please try again with the latest 1.0-SNAPSHOT? There's a magic one-line fix that might help...
Release is at hand if this is fixed :-)

Cheers

@vellamike
Copy link

On an AMD ubuntu machine I was able to resolve the issue by using the AMD-APP-SDK-v2.8.1.0 SDK.

@ochafik
Copy link
Member

ochafik commented Mar 18, 2015

This issue was moved to nativelibs4java/JavaCL#17

@ochafik ochafik closed this as completed Mar 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants