There is no change between v1.26.22.10 and v1.26.22.13 that could, even remotely, be related with that bug, that I never encountered myself. Clear your cache and see if it helps (a corrupted mesh could be cached).
In any case, this voluntary crash will be replaced with a simple warning in next release and will not impact you any more.