fix(DRM): broken keySystemsMapping due to multiple references of drmInfo #5388
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.
Different streams may share
drmInfo
references, which makes problem whenkeySystemsMapping
config is used. Assuming we have config:on the first access to the
drmInfo
objectDrmEngine
will set server fora.b.c
key system and replace key system tod.e.f
. On the 2nd access DrmEngine will not find server config ford.e.f
and thus will remove any server set.This issue can be easily mitigated by deduplicating
drmInfo
array.