You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e11a342
Browse filesBrowse the repository at this point in the historyBrowse files
Only render views that need to be rendered (with external texture & platform view support) (flutter#179874)
Fixesflutter#164320
Based on @knopp work in flutter#164322
This PR adds a dirty-view compositing optimization that skips
compositing for views that don't have any dirty render objects, so it
should improves performance in multi-view scenarios by avoiding
unnessacery work.
When a texture has new content, the framework now gets notified via a
new onTextureFrameAvailable callback from the engine. This marks the
texture's render object as needing paint, so its view is included in
compositing even when nothing else changed.
On Android, texture callbacks now use `markTextureFrameAvailable`
instead of `scheduleEngineFrame`. This is actually more efficient since
it reuses the existing layer tree rather than regenerating it. Other
platforms already used the correct path.
It also forces all views to composite when returning from background,
ensuring the display is properly refreshed after the app was paused.
On MacOS:
https://github.com/user-attachments/assets/9d8b21b5-0c61-40d9-aadc-8c5a4b76f20c
## Pre-launch Checklist
- [X] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [X] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [X] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [X] I signed the [CLA].
- [X] I listed at least one issue that this PR fixes in the description
above.
- [X] I updated/added relevant documentation (doc comments with `///`).
- [X] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [X] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [X] All existing and new tests are passing.
---------
Co-authored-by: Matej Knopp <[email protected]>
0 commit comments