Handle RDD crashes smoothly
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox85 | --- | fixed |
People
(Reporter: jya, Assigned: jya)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
The GPU RemoteDecoder will handle the case where the GPU process crashed elegantly. The GPU process will be restarted, and if needed HW decoding will be disabled if it continues crashing.
Video playback will temporary pause and resume, the error being completely transparent to the video element.
The RDD process on the other hand, when crashing will just cause a decoding error and stop. It will be restarted the next time we need a new decoder.
This behaviour was sufficient when the RDD only managed software decoding, and would pretty much never crash.
Now that the RDD can do HW decoding and use GPU image surface, it has the same chances of crashing as the GPU process.
We need to have RDD crashes handled like the GPU crashes.
|
||
Updated•4 years ago
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 1•4 years ago
|
||
|
|
Assignee | |
Comment 2•4 years ago
|
||
The RDD process startup being asynchronous make the operation trivial. Unlike with the GPU process, we can immediately tell the MediaFormatDecoder that a new decoder is needed when the RDD died.
Recovery will immediately occur with little visible interruption.
Depends on D98570
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/603841cbec35
https://hg.mozilla.org/mozilla-central/rev/cb44922f2e7a
Description
•