Yeah - not creating processes - just clicking in the UI
The vm trap logs often refer to classes that the user is nowhere and unlikely to have ever visited
Odd indeed!!
Problem is resolved by editing/saving the code - problem is finding that code.
I've started with the last working known map and working forwards, doing a build and running the app (multiple times) and wait for it to crash (anywhere between 1min and 24hrs+).
Instantiations are looking to provide a script that can verify the bytecode against the source code - should speed up the process in case it happens again in the future
Regards,
N