On 11/23/2015 06:59 AM, Anton Shterenlikht wrote: > The problem seems to be in 5.1. > It doesn't occur in 5.0 or 6.0. > Yes, we could not get the fix committed before 5.1 went out, caught in between. Thanks for asking. Jerry