As noted on the upstream bug this patch does not quite completely resolve this. I've only managed to reproduce this once, but it seems that there's probably an off-by-one error in the bounds checking.
I'm tracking this down now.
As noted on the upstream bug this patch does not quite completely resolve this. I've only managed to reproduce this once, but it seems that there's probably an off-by-one error in the bounds checking.
I'm tracking this down now.