It's possible lombok is directly to blame, but the stack is not particularly 'deep'. Possibly the disk your source files are on is really slow for some reason, or at least accessing one of the _super_ dirs of your workspace is really slow somehow. You can use the lombok.config stopBubbling directive to help (stick a lombok.config in your work space root with that directive, see the lombok docs on the config system about how to do this). That's just a wild
guess that config searching is partly the blame (it is in those traces).
Mostly I see a notification that it's waiting on a lock of the garbage collector. This happens all the time, so could be innocuous, but it might be an indication that your IDE just doesn't have enough max heap available to it. Lombok adds to the memory load of source representations.