Closed
Bug 1965557
Opened 1 year ago
Closed 1 year ago
[wmfme] reset hardware context for DRM_E_TEE_INVALID_HWDRM_STATE
Categories
(Core :: Audio/Video: Playback, task, P1)
Core
Audio/Video: Playback
Tracking
()
RESOLVED
FIXED
140 Branch
People
(Reporter: alwu, Assigned: alwu)
References
Details
Attachments
(1 file)
|
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
We recently received a report of getting DRM_E_TEE_INVALID_HWDRM_STATE, which is some thing we should handle properly.
| Assignee | ||
Comment 1•1 year ago
|
||
Pushed by alwu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3b0714d21dfc
reset hardware context for DRM_E_TEE_INVALID_HWDRM_STATE. r=media-playback-reviewers,padenot
Comment 3•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox140:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
| Assignee | ||
Comment 4•1 year ago
|
||
Comment on attachment 9486692 [details]
Bug 1965557 - reset hardware context for DRM_E_TEE_INVALID_HWDRM_STATE.
Beta/Release Uplift Approval Request
- User impact if declined/Reason for urgency: User might encounter a playback failure while playing video on Netflix.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce: No reproducible step, this is an error our partner reported to us.
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): No, it doesn’t introduce any new functionality. It’s just about properly handling the error to allow playback to continue without surfacing the failure.
- String changes made/needed: No
- Is Android affected?: No
Attachment #9486692 -
Flags: approval-mozilla-beta?
Comment 5•1 year ago
|
||
Comment on attachment 9486692 [details]
Bug 1965557 - reset hardware context for DRM_E_TEE_INVALID_HWDRM_STATE.
Approved for 139.0b9.
Attachment #9486692 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Updated•1 year ago
|
status-firefox139:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•