Sorry about this! It was a known crash which should now have been resolved in our recent hotfix 6.5.2: