Here are the minimal conditions needed to reproduce this issue:
- A Java package has a dependency on Lombok.
- A method uses Lombok's
@NonNull on a parameter.
- The first line of the method is a comment.
- The line after the comment is NOT empty.
- The
lombok.nonNull.exceptionType = JDK option is set in a lombok.config file.
If you open this project in VS Code with the redhat.java extension, any modification in that same file that does not break the above criteria (such as adding a comment on the last line and saving) will take 100% of one CPU core. Do it 5 times, and it will take 5 cores!
This high CPU usage stops after a while, but it makes the whole machine unresponsive if you make several modifications quickly.
You can use this minimal repo to reproduce the bug: ipkiss42/vscode-java-4052.
Here are the minimal conditions needed to reproduce this issue:
@NonNullon a parameter.lombok.nonNull.exceptionType = JDKoption is set in alombok.configfile.If you open this project in VS Code with the
redhat.javaextension, any modification in that same file that does not break the above criteria (such as adding a comment on the last line and saving) will take 100% of one CPU core. Do it 5 times, and it will take 5 cores!This high CPU usage stops after a while, but it makes the whole machine unresponsive if you make several modifications quickly.
You can use this minimal repo to reproduce the bug: ipkiss42/vscode-java-4052.