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

[BUG] #3610

Open
DerekSansom opened this issue Feb 19, 2024 · 2 comments
Open

[BUG] #3610

DerekSansom opened this issue Feb 19, 2024 · 2 comments

Comments

@DerekSansom
Copy link

Describe the bug
I've just used the lombok installer for my eclipse installation, and now elipse is unusable because every few seconds it pops up an error dialogue suggesting to shut eclipse and restart

THe error is a stack overflow from lombok

To Reproduce
download lombok, 1.18.30
run as jar and install in eclipse
run eclipse

Expected behavior
doesn't keep throwing stackoverflow error

Version info (please complete the following information):

  • Lombok version 1.18.30
  • Platform

Version: 2023-12 (4.30.0)
Build id: 20231201-2043

runs java 17

Additional context
on ubuntu mate 1.26.0

from eclipse log

!ENTRY org.eclipse.jdt.core 4 4 2024-02-19 16:22:50.100
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.StackOverflowError
at lombok.eclipse.EclipseAST.buildTree(EclipseAST.java:1)
at lombok.core.AST.buildWithField0(AST.java:394)
at lombok.core.AST.buildWithField(AST.java:292)
at lombok.eclipse.EclipseAST.drill(EclipseAST.java:532)
at lombok.eclipse.EclipseAST.buildStatement(EclipseAST.java:527)
at lombok.eclipse.EclipseAST.buildTree(EclipseAST.java:367)
at lombok.eclipse.EclipseAST.buildTree(EclipseAST.java:1)
at lombok.core.AST.buildWithField0(AST.java:394)
at lombok.core.AST.buildWithField(AST.java:292)

@janrieke
Copy link
Contributor

You probably have a large source file in your project, and Lombok runs into the stack size limit when processing it. Try setting "-Xss2m" in your eclipse.ini.

@rspilker
Copy link
Collaborator

@DerekSansom Have you been able to test using the suggestion from @janrieke?

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

3 participants