Mobile/Firefox for Android/shutdown decoder
- 1 Overview
- 2 Overall Project Health
- 3 Target Milestone
- 4 Engineer Owner
- 5 QA Contact
- 6 MVP Scope-Bug Tracking
- 7 Signoff-Report issued on March21 by Bogdan Surd
- 8 UX Spec
- 9 others
Suspending video element's video decoder, when the video element is in background tabs or is invisible even in the foreground tab, is a Firefox feature that reduces CPU/GPU & memory usage.
The mechanism is that, when a video element is invisible, we replace its original video decoder with blank video decoder which only produces white frames with right resolution and right time information. The original video decoder is released and the black video decoder is light so that we reduce CPU/GPU & memory usage.
The trade-off is that, while the suspended-video-element is switched back to be visible again, we should resume its original video decoder. The resuming operation must be asynchronous and might be time-consuming which depends on the resolution of the video file and whether it contains audio tracks or not.
The following is a step-by-step description of suspending decoder working flow.
- At the very beginning of the decoding framework, the raw media data is sent to demuxer.
- Demuxer helps to separate a combined signal, e.g., a streaming can be separated into audio data and video data by demuxer. After that, audio and video data are sent to audio and video decoder separately.
- In data decoding period, audio decoder keeps working as normal because a user may be listening to the music. But, Firefox uses a blank video decoder to replace current video decoder if the video element is invisible.
Overall Project Health
Tzuhao Kuo [:kaku]
Ioana Chiorean <email@example.com>
Bogdan Surd, QA [:bogdan] <firstname.lastname@example.org>
MVP Scope-Bug Tracking
- bug 1293963 -[Meta] Suspend-video-decoder: phase-1 shipping
17 Total; 1 Open (5.88%); 13 Resolved (76.47%); 3 Verified (17.65%);
29 Total; 0 Open (0%); 26 Resolved (89.66%); 3 Verified (10.34%);
11 Total; 1 Open (9.09%); 10 Resolved (90.91%); 0 Verified (0%);
Signoff-Report issued on March21 by Bogdan Surd
Feature testing status: COMPLETED
performed Smoke and Exploratory testing on Fennec Nightly 55.0a1 build on multiple Android versions (from 5.1.1 to 7.0).
Overall feature status after testing: GREEN
One new issues was found during the Nightly 55.0a1 testing related to the "Suspend Video Decoder Elements" feature.
Recommendation from QE: SHIP IT
Based on the test results, I'm signing off this feature for the Aurora merge.
9 Total; 1 Open (11.11%); 5 Resolved (55.56%); 3 Verified (33.33%);
- UX Spec : [https://mozilla.invisionapp.com/share/K48PCVSEM UX Spec
Decoder resuming latency
While the suspended-video-element is switched back to be visible again, we should resume its original video decoder. The resuming operation must be asynchronous since we don't want to block the main thread and might be time-consuming which depends on the resolution of the video file and whether it contains audio tracks or not.
Currently, we have no way to boost the resuming time, however, we have telemetries for collecting the needed time of different resolutions on different platforms.