Unresponsive Eclipse neon.3, RHEL7 w/ oracle_jre_8 in virtualbox - eclipse

Running Eclipse neon.3 in a RHEL7 virtualbox VM, with 8GB total RAM. On occasion, Eclipse becomes completely unresponsive and the OS system monitor shows the CPU cores taking turns to go to 100%.
eclipse.ini:
-startup
plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.401.v20161122-1740
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.8
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
jvisualvm shows that the big consumer is
org.eclipse.equinox.launcher.Main.main()
I watch as the Total Time goes up 1000 ms every second. Looks like a busy loop in what looks like the gtk_OS hooks.
The RAM profile for eclipse looks like the Himalayas, so clearly a memory leak.
Anyone notice this behaviour and know what to do about it?
Thanks,
Robin
p.s. very temporary screen grab https://img42.com/0USxM
p.p.s. doanloadable image of jvisualvm here, https://expirebox.com/download/932e3dcaf6a83022d37c567713f2023b.html

"What I know is that the problem completely disappears after turning off +UseG1GC ."
according to:
https://www.eclipse.org/forums/index.php/t/1082145/
I had the same problem which disappeared after I updated eclipse to oxygen version.

Related

STS.ini can't set heap more than 1024m (Eclipse configuration)

this is my sts.ini
-vm
C:/Program Files (x86)/Java/jdk1.6.0_24/bin/javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222
-product
com.springsource.sts.ide
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
584M
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xmn128m
-Xms256m
-Xmx1024m
-Xss1m
-XX:PermSize=128m
-XX:MaxPermSize=584m
My STS(Spring Tool Suite) is keep falling on low memory. I tried to increase memory of heap, but if i set -Xmx greater than 1024m (for exeample -Xmx2048m) it writes "Could not create Java Virtual Machine". I have pc with 16GB Ram and OS Windows 7 Professional 64bit and using 32bit 1.6 Java.
How can I give to my STS more memory to prevent the falling if this doesn't work. I tried to google it but I didn't find anything useful.
This limitation is indeed caused by using the 32bit JVM. To use more heap space for your STS or Eclipse installation, please download the 64bit version of it and use it with a 64bit JVM for your Windows system.

Eclipse Luna stop working in Debian when pop-up open

every time I go to the Eclipse-luna IDE and enter a line of code in a class that I created and code assist opens the pop-up with suggestions, stop working the eclipse and only runs again if I kill process and re-run the eclipse.
My OS is the latest stable version of kali (debian based with kernel 3.18.3) x86_64 with open-jdk 1.6 and 1.7 installed by default in the system.
Thank for all.
I could figure out the problem and solve the same describe below how it was done so to help someone who is having the same problem. To begin i'm using the latest stable version of eclipse-luna downloaded direct with the site or using wget. Open your eclipse.ini file and exactly one row before --launcher.appendVmargs enter these two lines below:
`
--launcher.GTK_version
2
`
and are ready your eclipse'll be already functioning normally in debian remembering that I previously had to change -showsplash to -nosplash.
Below I leave an exact copy of my eclipse.ini remembering that already means tuned.
`
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20150204-1316
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
-nosplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m
--launcher.defaultAction
openFile
--launcher.GTK_version
2
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=512m
-Xms80m
-Xmx1024m
`
Thanks for all

Eclipse scolling very slow on Mac OS X 10.8.5

I have Eclipse (Kepler) on Mac osx 10.8.5, everything works out pretty good, except that the scrolling is lagging like crazy... I have followed some suggestions to update java to java 7, and i see that eclipse is using
/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/jre/lib/libjava.dylib
I also increased eclipse jvm to use bigger memory size. Here's my eclipse.ini:
-startup
../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835
-product
org.eclipse.epp.package.standard.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XX:PermSize=512m
-XX:MaxPermSize=1028m
-Xms256m
-Xmx1028m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
So I'm not sure what else I need to do to fix this. Anybody got any suggestions?
Have the same issue with MBP Retina and OSX 10.9 with JRE 1.6. I think that it is related to not optimized drawing of content in editor's window. If you f.e. shrink eclipse's window it will operate faster. In full screen mode it took up to 80% of one processor's core.
BTW there is already a bug report for that issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=366471

eclipse crashes while trying to build

I was wondering if someone could explain why my eclipse is crashing. Eclipse says its trying to build and then there is a message not responding and I receive this message as eclipse close in figure 1
figure 1
The startup jvm memory allocated to eclipse seems to be low, in the screenshot provided:
-Xms40m -Xmx512m
Increasing these values might provide eclipse more memory to build project.
(Try closing all unused projects in the eclipse workspace)
Assuming your machine has RAM > 2-3 GB,
Modify the file eclipse.ini (in your case at C:\eclipse\eclipse.ini)
Update values of '-Xms' and '-Xmx' to following
....
-Xms512m
-Xmx1024m
The problem is Memory dedicated to eclipse .
this is the way my problem solved
fist :~>locate eclipse.ini
/home/ your - user /eclipse/eclipse.ini
Second
vi /home/ your - user /eclipse/eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20150204-1316
-product
org.eclipse.epp.package.cpp.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
512m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=1024m
-Xms512m
-Xmx2048m
Then change This lines
--launcher.XXMaxPermSize
512m // mine was 256
-XX:MaxPermSize=1024m // mine was 512
-Xms512m // mine was 40
-Xmx2048m // mine was 512
Done :)

How can I give eclipse more memory than 512M?

I have following setup, but when I put 1024 and replace all 512 with 1024, then eclipse won't start at all. How can I have more than 512M memory for my eclipse JVM?
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-product
com.springsource.sts.ide
--launcher.XXMaxPermSize
512M
-vm
C:\Program Files (x86)\Java\jdk1.6.0_18\bin\javaw
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms512m
-Xmx512m
-XX:MaxPermSize=512m
I've had a lot of problems trying to get Eclipse to accept as much memory as I'd like it to be able to use (between 2 and 4 gigs for example).
Open eclipse.ini in the Eclipse installation directory.
You should be able to change the memory sizes after -vmargs up to 1024 without a problem up to some maximum value that's dependent on your system. Here's that section on my Linux box:
-vmargs
-Dosgi.requiredJavaVersion=1.5
-XX:MaxPermSize=512m
-Xms512m
-Xmx1024m
And here's that section on my Windows box:
-vmargs
-Xms256m
-Xmx1024m
But, I've failed at setting it higher than 1024 megs. If anybody knows how to make that work, I'd love to know.
EDIT: 32bit version of juno seems to not accept more than Xmx1024m where the 64 bit version accept 2048.
EDIT: Nick's post contains some great links that explain two different things:
The problem is largely dependent on your system and the amount of contiguous free memory available, and
By using javaw.exe (on Windows), you may be able to get a larger allocated block of memory.
I have 8 gigs of Ram and can't set -Xmx to more than 1024 megs of ram, even when a minimal amount of programs are loaded and both windows/linux report between 4 and 5 gigs of free ram.
Here is how i increased the memory allocation of eclipse Juno:
I have a total of 4GB on my system and when im working on eclipse, i dont run any other heavy softwares along side it. So I allocated 2Gb.
The thing i noticed is that the difference between min and max values should be of 512. The next value should be let say 2048 min + 512 = 2560max
Here is the heap value inside eclipse after setting -Xms2048m -Xmx2560m:
Care and feeding of Eclipse's memory hunger is a pain...
http://www.eclipsezone.com/eclipse/forums/t104307.html
https://bugs.eclipse.org/bugs/show_bug.cgi?id=188968
https://bugs.eclipse.org/bugs/show_bug.cgi?id=238378
More or less, keep trying smaller amounts til it works, that's your max.
I don't think you need to change the MaxPermSize to 1024m. This works for me:
-startup
plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-product
org.eclipse.epp.package.jee.product
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms256m
-Xmx1024m
-XX:PermSize=64m
-XX:MaxPermSize=128m
You can copy this to your eclipse.ini file to have 1024M:
-clean -showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Xms512m
-Xmx1024m
-XX:PermSize=128m
-XX:MaxPermSize=256m
While working on an enterprise project in STS (heavily Eclipse based) I was crashing constantly and STS plateaued at around 1GB of RAM usage. I couldn't add new .war files to my local tomcat server and after deleting the tomcat folder to re-add it, found I couldn't re-add it either. Essentially almost anything that required a new popup besides the main menus was causing STS to freeze up.
I edited the STS.ini (your Eclipse.ini can be configured similarly) to:
--launcher.XXMaxPermSize
1024M
-vmargs
-Xms1536m
-Xmx2048m
-XX:MaxPermSize=1024m
Rebooted STS immediately and saw it plateau at about 1.5 gigs before finally not crashing
Configuring this worked for me:
-vmargs -Xms1536m -Xmx2048m -XX:MaxPermSize=1024m
on Eclipse Java Photon June 2018
Running Windows 10, 8 GB ram and 64 bit.
You can extend -Xmx2048 -XX:MaxpermSize= 1024m to 4096m too, if your computer has good ram.Mine worked well.