The screen resolution for the original bug was 1366x768.
On a 1600x900 monitor with the Intel HD4000, I can also see this bug.
It's clear that the rectangle isn't moving too far to the left. Instead, it is occasionally showing positions to the right: old positions are being briefly rendered after new positions have already appeared. This causes the bouncing effect.
Imagine UDP packets arriving out-of-order, so that an old packet overrides a new packet's information. That's what I'm seeing here, but with framebuffers instead of packets.
The screen resolution for the original bug was 1366x768.
On a 1600x900 monitor with the Intel HD4000, I can also see this bug.
It's clear that the rectangle isn't moving too far to the left. Instead, it is occasionally showing positions to the right: old positions are being briefly rendered after new positions have already appeared. This causes the bouncing effect.
Imagine UDP packets arriving out-of-order, so that an old packet overrides a new packet's information. That's what I'm seeing here, but with framebuffers instead of packets.