You could try to get nearer to the point, it fails, if you run your script from command line with option -s, so at least the logging is available after the crash.
If you want to watch "the road to hell", you might make some intermediate regions/matches visible with Region.highlight(1) and/or watch your script in slow motion while drinking a cup of coffee or what ever you like.
Since the problem is with awt.dll, I am rather sure it has something to do with the bug I mentioned already (so currently no solution available with your system)
You could try to get nearer to the point, it fails, if you run your script from command line with option -s, so at least the logging is available after the crash.
If you want to watch "the road to hell", you might make some intermediate regions/matches visible with Region.highlight(1) and/or watch your script in slow motion while drinking a cup of coffee or what ever you like.
Since the problem is with awt.dll, I am rather sure it has something to do with the bug I mentioned already (so currently no solution available with your system)