Skip to content

VPLAY-12689 Crash from teardown on HDCP error#2987

Open
sayanurag wants to merge 1 commit into
support/8.4.4.0from
feature/VPLAY-12884_HDCP_error
Open

VPLAY-12689 Crash from teardown on HDCP error#2987
sayanurag wants to merge 1 commit into
support/8.4.4.0from
feature/VPLAY-12884_HDCP_error

Conversation

@sayanurag
Copy link
Copy Markdown

Reason for change: On processing a gst HDCP error, flush with teardown is called without stopping stream injection leading to an abort
Test Procedure: See ticket
Risks: low

Reason for change: On processing a gst HDCP error, flush with teardown is called without stopping stream injection leading to an abort
Test Procedure: See ticket
Risks: low

Signed-off-by: Anurag Krishnan <akrish513@cable.comcast.com>
Copilot AI review requested due to automatic review settings May 29, 2026 10:03
@sayanurag sayanurag requested review from a team as code owners May 29, 2026 10:03
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Bumps the aamp recipe to pick up a fix for a crash that occurs during teardown triggered by an HDCP error (flush-with-teardown was called without first stopping stream injection).

Changes:

  • Update SRCREV_aamp to the new commit containing the HDCP teardown crash fix.
  • Bump PV:pn-aamp from 2.11.10e to 2.11.10_1e.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
conf/include/generic-srcrev.inc Updates the aamp SRCREV to the fix commit.
conf/include/generic-pkgrev.inc Bumps the aamp package version to reflect the new revision.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-advanced-security
Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants