As a temporary workaround, you can import these settings without a hitch if your Open Tool Window is open. Go to View > Tool Windows > Open and that will bring up the tool window. Then import your settings. You can then close the Open Tool Window if you like. I'll include a fix for this in the cumulative hotfix and will update this thread when it's ready.
The offset can help you determine where the error occurred. tbopen.ex is just the compiled Slick-C byte code of tbopen.e, one of our shipped macros. Every time you successfully load a Slick-C file, one of these .ex files is created.
To find the place where the stack happened, you can double-click on the line in the Slick-C stack window (the middle picture that you posted). Double-click on the top most line of the stack (tbopen.ex 671 ...) and that file will open with the cursor in that position. You could also double-click on any line in the stack window that lists a .ex file and offset to be taken to that position.
Of course, if you get a stack like that, we'd like to know about it, too, so we can fix it for everybody.
