Repository navigation
Add Low resource mode setting for older devices - #49
Merged
Merged
Conversation
The Browser and Reader tabs each keep their own InAppWebView alive (KeepAliveWrapper in the TabBarView), so on memory/CPU-constrained devices two web renderer processes run at once. The new opt-in setting (Settings > Behavior > Low resource mode, off by default) pauses the WebView of a hidden tab (WebView.onPause / WebView2 TrySuspend, media paused everywhere) and resumes it when its tab is selected, requires a user tap before media plays in the Browser tab, sets Android rendererPriorityPolicy waivedWhenNotVisible so hidden pages can be reclaimed under memory pressure, and suspends both WebViews while the app is backgrounded. Reader extraction still runs against the live browser view before it is paused. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Browser and Reader tabs each keep their own InAppWebView alive, so on memory/CPU-constrained devices two web renderer processes run at once.
Adds an opt-in Low resource mode (Settings → Behavior, off by default, changelog under 1.3.0):
WebView.onPause/ WindowsTrySuspend, media paused on all platforms) and resumes it when its tab is selected; Reader extraction still runs against the live browser view before it is paused.mediaPlaybackRequiresUserGesture).rendererPriorityPolicywithwaivedWhenNotVisibleso the system can reclaim memory from hidden pages.Verified:
flutter analyzeclean (no new issues) andflutter testpasses (1381 tests).