Originally Posted by uau
Queuing up to 8 frames worked if doing nothing else, but trying to do other operations like upload video surfaces while having two or more unshown surfaces queued for display caused the driver to use a lot of CPU (could have been a busyloop until there was only one yet undisplayed surface). This at least looks like a clear implementation problem.
We've identified a fix for this issue. It will be included in a future driver release.