Reply #1 Top

I'm getting this exact same bug in 1.19i.