Eclipse for Cuda (nsight) crashes with Java heap space,unhandled event Loop exception error

Today found Nsight this artifact. is an eclipse-specific Cuda IDE. But unfortunately always crashes IDE quits.

These English error prompts appear:

Java Heap Space

An internal error occurred during:update Monitor

Unhandled Event Loop exception

Finally toss a sudden, found the solution.

Open configuration file Nsight.ini

Gedit/usr/local/cuda-5.5/libnsight/nsight.ini

See

--LAUNCHER.DEFAULTACTIONOPENFILE-VM. /jre/bin/java-vmargs-xx:compilecommand=exclude,java/lang/reflect/array,newinstance-dosgi.requiredjavaversion= 1.6-xms40m-xmx256m-xx:maxpermsize=256m

I changed-xmx256m directly to-xmx1024m. is to increase some heap memory.

Then it looks good, haha!

！！

References

1

Eclipse.ini:the memory for the VM running eclipse

The Eclipse installation folder changes to-xms800m-xmx800m in Eclipse.ini (PS: Let's say this step is OK. There is no need for a second step. I have conquered it by this.)

http://blog.csdn.net/wulongtiantang/article/details/7544883
Java Heap space Eclipse

2
Java heap Space is the reason the JVM is running out of memory when executing the program
Eclipse has the boot parameters to set the JVM size. Since Eclipse executes its own JVM, the JVM size set in Eclipse.ini is not the size of the JVM used to detail a program's execution, regardless of the size of the JVM that the detailed program executes.

Http://blog.sina.com.cn/s/blog_6e6315e30100u9b6.html
Eclipse Java Heap Space Solution


3
To illustrate the meaning:
-xms128m
Represents the JVM heap (heap memory) minimum size 128MB, initial allocation
-xmx512m
Represents the maximum consent size of the JVM heap (heap memory) 256MB, on demand.
http://blog.csdn.net/zhuxiaowenlinda/article/details/7863986
JVM Virtual machine options: Xms Xmx permsize maxpermsize Differences

Eclipse for Cuda (nsight) crashes with Java heap space,unhandled event Loop exception error