Thaks for the report and sorry about that! It's pretty mysterious, but it looks very similar to the one reported here:
Can you reproduce the problem with the same example, or is it non-deterministic? There's realy only one place in the code that changed and that could cause this, and I'm pretty sure I already fixed it and it'll go out with the v1.10.1 release (likely this week)
