Thank you for your report. Based on our data it should behave similarly on 10.1, so it would be good if you can try the same procedure that led to crash in 10.3 on 10.1 (we are able to reproduce it on 10.1 too, maybe it is just less common).
We are still trying to find a workaround for this, but it is very hard to do so.
1 Like