Comment 5 for bug 1379685
Revision history for this message
| Daniel van Vugt (vanvugt) wrote Re: Full screen (bypassed) surfaces are missing frames and appear to freeze with swap interval 0 | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
"Best visual experience" is easily achieved if we just intelligently scale up to quad-buffers when required. Then you never lose any frames and never tear. I will have to revive the aforementioned "double" branch and reintroduce the demand heuristic.
It's not just bypass either. Multi-monitor can lead to the same situation with frame dropping surfaces. It's quite plausible that two different compositor buffers are being held, resulting in only one left over for the client and so the newest frame gets dropped.
Dropping the newest frame on a surface that's rendering continuously is just a degradation in visual quality. But in a render-on-demand app, it can be catastrophic - resulting in an apparently frozen window with no new frames displayed for an unpredictably long time.