Comment 6 for bug 1418081
Revision history for this message
| Alexandros Frantzis (afrantzis) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> I think for the complex composited desktop case, this is OK. It's perfectly fine performance wise on a desktop
> if you have a window producing new frames that the compositor wakes up.
The occluded surface doesn't need to continuously produce frames. As long as a surface has an available frame and is not rendered (e.g. it's occluded), the compositor will composite at full speed (60FPS).
> For mobile devices, this would be a non-issue. Because Ubuntu-touch freezes them with SIGSTOP so they can't produce
> new frames while occluded.
For the same reason mentioned above, SIGSTOP doesn't help.