Memory increases dramatically on eclipse Kepler SR2 after lombok

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start eclipse with lombok - it starts up successfully
  (using about 1.1G)
2. while using eclipse memory usage increases double
  (using about 2G)
  and it slows down eclipse too.

What is the expected output? What do you see instead?
- Memory usage shouldn't be doubled by 

What version of the product are you using? On what operating system?
- Windows 7
- jdk1.7.0_51
- eclipse Kelper SR2
- lombok 1.14.0

Please provide any additional information below.

eclipse.ini 
-vm
C:/ISDEnvironment/installs/Java/jdk1.7.0_51/bin/javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140116-2212
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.7
-Xms500M
-Xmx3000M
-XX:+UseConcMarkSweepGC
-javaagent:.\lombok.jar
-Xbootclasspath/a:.\lombok.jar
-XX:MaxPermSize=256m

Original issue reported on code.google.com by joseph...@gmail.com on 30 May 2014 at 6:18

[GoogleCodeExporter]

I'm almost positive this is 1.14.0 related, and a bug in the config system. Do 
you still see this memory usage in 1.12.6?

Original comment by reini...@gmail.com on 1 Jun 2014 at 8:16

[GoogleCodeExporter]

Do you see anything in the error log? It's a view that can be opened from 
eclipse's window menu.

Original comment by reini...@gmail.com on 1 Jun 2014 at 8:18

[GoogleCodeExporter]

FWIW, I was getting OOM with Eclipse eating over 4GB as I was trying some 
configuration-implementing version from git (unfortunately, I don't know which 
one). With the current version the problem is gone (memory usage 1.2 GB).

Original comment by Maaarti...@gmail.com on 1 Jun 2014 at 11:31

[GoogleCodeExporter]

I downgraded to 1.12.6 and looks more promising.
I have used eclipse about couple of hours so far, but no symptom of the 
increase of memory use.

It seems like like the issue with 1.14.0.

Original comment by joseph...@gmail.com on 2 Jun 2014 at 1:39

[GoogleCodeExporter]

I can confirm I get the same behavior with Lombok 1.14.0 in Eclipse.
I have a few errors regarding Lombok, but they occurred around 30 minutes 
before I had to close Eclipse due to a "java.lang.OutOfMemoryError: Java heap 
space" exception.

The OOM exception came after a few minutes of severe slowdown in Eclipse.

I attached the Lombok exceptions I got in the file.
Note that I do not know if they are related to the actual OOM exception, but I 
had no issues before updating to Lombok 1.14.0.

Original comment by gabriel....@gmail.com on 6 Jun 2014 at 2:52

Attachments:

• lombok.txt

[GoogleCodeExporter]

I tried 1.14.2 and same problem occurs.

Original comment by joseph...@gmail.com on 18 Jun 2014 at 5:06

[GoogleCodeExporter]

I have been running 1.14.2 in Eclipse Kepler SR2 for a few days now.
I have NOT encountered any major slowdown or any Out of Memory exceptions since 
the update.

I was having those exceptions daily with 1.14.0 (see comment #5) and now I have 
no more.

Original comment by gabriel....@gmail.com on 19 Jun 2014 at 4:03

[GoogleCodeExporter]

joseph: We can't take action on such a comment without more detail. What's in 
your error log? Do you run into lombok issues or is massively increased memory 
load the only symptom?

Original comment by r.spilker on 24 Jun 2014 at 6:52

[GoogleCodeExporter]

It is just symptom but no error as explained. 
And it has happened all the time. 
I turned lombok off from eclipse.ini and memory usage stayed same.
Then, I put lombok configuration back on and memory usage increased (doubled) 
after 1-2 hours of use.

I didn't do anything special while using eclipse.

I just opened java editor and coding the java classes and some classes contain 
lombok @Data annotation. 
I was using general editor feature finding out available methods for a class 
(ctrl+shift) while coding.

The only thing I can provide is screenshot of the memory use for eclipse, but I 
don't think it will be much useful.

Original comment by joseph...@gmail.com on 24 Jun 2014 at 10:09