Comment 1 for bug 1418081

Unfortunately this sounds kind of right.

We failed to consume all buffers last frame, and it's quite possible that the shell has changed something that allows them to be consumed on the next. So the right answer is indeed to schedule a frame immediately.

To solve this for everyone we would probably have to distinguish between the _reasons_ for a buffer not getting consumed. Starts to sound messy.