I've also had some oddities with crashing, only on opening Statement rather than trigger logs (which I've not tried), and then only on, so far, one particular profile. It opens a blank statement, and corrupts the entire profile requiring it to be recreated.
Given it's one profile suggests it's an issue with a trigger (I think the settings should be moreorless the same), but damned if I can work out which one because of the corruption issue to narrow down the guilty party. :/ Might be viable with a TM license and going through it offline repeatedly...
Also, if one instance crashes (even without a corruption), the remaining open instance(s) prevent the crashed profile alone being reopened ("There's already a profile with this name open" No, there isn't!
), requiring all instances to be shut down, something it feels risky to do given the need to then hammer BF to recreate the market lists.