Having a quick look it appears this error is triggered by the call to LWJGL2's Display.isActive() method.
From the crash stack it originates from the native call Java_org_lwjgl_opengl_MacOSXDisplay_nIsFocused, which
is composed of two checks to NSWindow methods (isKeyWindow & firstResponder):
return (jboolean)([[window_info->view window] isKeyWindow] && [[window_info->view window] firstResponder] == window_info->view);
Thereafter the stack shows the crash originates from within the call to [NSWindow firstResponder].
I can't really see any memory management going on in the LWJGL code that would cause the overflow. Therefore the crash appears to be originating from inside the firstResponder method. If it doesn't happen in previous versions of MacOS, I'm guessing its probably an OS bug or some sort of change in behaviour in how that method worked.
From just looking at the LWJGL code (so not 100% sure) I don't think the check for "&& [[window_info->view window] firstResponder] == window_info->view" is even needed for a stand-alone LWJGL Display window and is probably there for checking if the Display.isActive() when embedded inside an AWT window. So a quick hack/workaround without looking further at the cause of the overflow may be to just disable this additional check (inside org_lwjgl_opengl_Display.m) if there is no parent window (AWT Parent), therefore avoiding the call to the firstResponder method altogether.
In the long term, you really should make the switch to LWJGL3. LWJGL2 being unmaintained (surprising it still works as much as it does) is only going to get more and more broken (especially on Mac's as Apple make regular changes to their API's).