1896931 - (media3) [meta] ExoPlayer: remove or migrate to Media3?

Status: NEW

(Core :: Audio/Video, task)

Description

[Jim Mathies [:jimm]]

Discussion around what we want to do with ExoPlayer code in GeckoView.

Comment 1

[Chris Peterson [:cpeterson]]

Exoplayer is the source of many Firefox Android's content process OOMs:

https://crash-stats.mozilla.org/search/?signature=~exoplayer&product=Fenix&product=Focus&_facets=signature&_facets=version&_facets=major_version&_facets=cpu_arch&_facets=android_version&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature

Comment 2

[Dan]

Why did we move away from ExoPlayer to HLS????

Comment 3

[John Lin [:jhlin][:jolin]]

Disabling HLS in bug 1896932 makes the content in bug 1802969 unplayable. (It was originally playable with an audio issue.) It seems there are sites that use hls.js on desktop but have some web compatibility issues on mobile.

Comment 4

[Dan]

Comment 2, Chris?

Comment 5

[Chris Peterson [:cpeterson]]

Why did we move away from ExoPlayer to HLS????

Firefox Android used the ExoPlayer to implement native support for HLS in Gecko. This bug removed the outdated ExoPlayer, expecting websites would fall back to the hls.js library. But there are some issues with hls.js we need to investigate.

Comment 6

[Dan]

Oooh ExoPlayer is outdated, ok.

Comment 7

[Chris Peterson [:cpeterson]]

There are two reasons we might move from Exoplayer to Media3:

• Avoiding the Exoplayer OOM crashes (bug 1923711)
• Exoplayer is no longer maintained and Media3 is Google's replacement

https://github.com/google/ExoPlayer
https://developer.android.com/media/media3/exoplayer