What you described looks like the same issue demonstrated here. We currently have an internal ticket for this issue.