On Tue, 3 Nov 2020 08:45:20 GMT, Matthias Baesken <mbaes...@openjdk.org> wrote:
> Currently in case of occurences of an NSException in runAWTLoopWithApp we
> catch the exception just print a simple error message like this :
>
> 2020-10-30 15:28:33.027 java[634:8435] Apple AWT Startup Exception: Cannot
> lock focus on image <NSImage 0x7fd350d7f9f0 Size={0, 0} RepProvider=(null)>,
> because it is size zero.
> 2020-10-30 15:28:33.306 java[634:8435] Apple AWT Restarting Native Event
> Thread
>
> But we omit the callstack and loose valuable information. This change adds
> the callstack to the output.
To me this looks like a good idea. In our current customer case this
information would have greatly helped analysis. However, I'd like to see an
opinion from one of the experts in that area on whether that's appropriate here.
-------------
Marked as reviewed by clanger (Reviewer).
PR: https://git.openjdk.java.net/jdk/pull/1032
