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

Performance decrease when using lombok 1.14 with STS 3.6.0 #749

Open
lombokissues opened this issue Jul 14, 2015 · 6 comments
Open

Performance decrease when using lombok 1.14 with STS 3.6.0 #749

lombokissues opened this issue Jul 14, 2015 · 6 comments

Comments

@lombokissues
Copy link

Migrated from Google Code (issue 714)

@lombokissues
Copy link
Author

👤 lirany2   🕗 Jul 28, 2014 at 12:51 UTC

What steps will reproduce the problem?

  1. Install 1.14.4 lombok.jar in STS 3.6.0 (eclipse 4.4)
  2. When using code assist (ctrl+space) in some classes it is very slow.
  3. CPU is also very high during this time.

When reverting to lombok 1.12.6 in eclipse it works much faster.

I attached a visualvm profiling snapshot from an event where it takes a long time for the code assist to complete.

@lombokissues
Copy link
Author

👤 lirany2   🕗 Jul 28, 2014 at 12:51 UTC

🔗 visualvm-profiler-eclipse.nps

@lombokissues
Copy link
Author

👤 wsalik   🕗 Sep 18, 2014 at 13:42 UTC

I am facing same issue with even lombok 1.12.6. and sts 3.6 code assist and even copy text by ctrl+c became painfully slow.

@lombokissues
Copy link
Author

👤 yudhistira.arya.rukmana   🕗 Dec 10, 2014 at 12:49 UTC

I'm facing the same issue in Intellij IDEA 14.0.1 with lombok plugin (very slow make/compile time). After downgrading to lombok-1.12.6.jar everything is snappy as usual.

@lombokissues
Copy link
Author

End of migration

@hendimarcos
Copy link

I'm using 1.18.2 and am having the same problem of performance in Ctrl + C and Ctrl + spaces
Fedora 28 + wayland
Eclipse Photon + RedHat Developer Tools
Openjdk version "1.8.0_181"

lianhaijun pushed a commit to lianhaijun/lombok that referenced this issue May 8, 2020
…ok#749)

It would be nice to inform users that private and final modifiers
on fields are redundant in classes marked with @value.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants