Closed Bug 2083015 Opened 1 month ago Closed 1 month ago

Switch Android's RemoteDataDecoder to use a task queue and try to create the CodecProxy during construction

Categories

(Core :: Audio/Video, defect)

All
Android
defect

Tracking

()

RESOLVED FIXED
160 Branch
Tracking Status
firefox160 --- fixed

People

(Reporter: aosmond, Assigned: aosmond)

References

Details

Attachments

(1 external file)

This is desirable for a few reasons:

  1. Switches us to do Android decoder work on a task queue instead of the same thread as whatever calls Init. This matches the architecture we do in most other places.
  2. Creating the decoder at construction instead of Init allows us to fail and fallback to another PDM (e.g. the VP9 HW decoder cannot support the requested size, fallback to ffvpx), and
  3. This will make the WPT media capabilities tests behave the same between the Java and NDK backends.
Blocks: 2082956

RemoteDataDecoder now owns its task queue, so the Java codec can be created and
configured during decoder creation. If that fails, PDMFactory can fall back to
another decoder module, as it does for the FFmpeg MediaCodec decoder.

Pushed by aosmond@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/1439ec7644bd https://hg.mozilla.org/integration/autoland/rev/bd263aa44ca0 Create the Java MediaCodec decoder before resolving AndroidDecoderModule::AsyncCreateDecoder. r=media-playback-reviewers,alwu
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 160 Branch
QA Whiteboard: [qa-triage-done-c161/b160]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: