Fix battery drain from Web Audio #29203
Open
+10
−0
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.
Element audio notifications cause a small, but noticeable battery drain on my Linux laptop, both with Firefox and Chromium. The drain is constant and disappears only after closing Element tab or the browser. In Firefox merely launching Element starts the battery issues, in Chromium it happens after the first notification arrives.
Here's a screenshot from
pw-top
long after a notification happened:pw-cli info
confirms the bogus stream is an Element tab.Web Audio doc says: "The suspend() method of the AudioContext Interface suspends the progression of time in the audio context, temporarily halting audio hardware access and reducing CPU/battery usage in the process — this is useful if you want an application to power down the audio hardware when it will not be using an audio context for a while."