Sorry to hear this. I’m sad to say we’re not able to manually compensate in this situation, but we’d like to resolve the underlying issue to prevent unfortunate situations like this.
If you could please share your crash report or corresponding console log, I can make sure this is looked in to: