M1 Only, so did you test linux, windows and macos?
The more I investigate this the more I think it’s an uncaught TypeMismatchException.
If I set the build project to Intel and run it on my M1 MacBook Pro (under Rosetta) I get the crash less often. When it does crash, I sometimes get a TypeMismatchException (not always).
I’ve refactored the code extensively as I was using a Dictionary subclass to store Text values. I think there may have been an issue where I was checking to see if the value stored in the dictionary matched a String literal I typed in the IDE. I think since the value in the dictionary was Text that was causing a TypeMismatchException. Of course I can’t be sure since the exception was hardly ever being captured.
So far, the crash is gone…
I shall continue to stress test.
This certainly still seems a bug in the framework (and my code). Exceptions should always be caught shouldn’t they?
1 Like
Technically they should raise App.UnhandledException if you don’t catch them in your code, yes.