Hey,
so far, I have not encountered this issue with the latest patch 2017.2.0p2 so I think it might be fixed. The patch release notes do not provide any information on the related ticket #930408 though.
However, after updating to 2017.2.0p2, unfortunately I’ve been experiencing a completely new assertion issue.
New thread about it here .