Can you please check if the issue still occurs with the new version 1.0.20 that just came out. If so, please do send a new crash report.