Skip to content

[GStreamer] Critical warning when updating video sink stats of a player in error state - #1388

Merged
cadubentzen merged 1 commit into
wpe-2.38from
wpe-2.38-updateVideoSinkStatistics
Aug 21, 2024
Merged

[GStreamer] Critical warning when updating video sink stats of a player in error state#1388
cadubentzen merged 1 commit into
wpe-2.38from
wpe-2.38-updateVideoSinkStatistics

Conversation

@cadubentzen

Copy link
Copy Markdown

This is a backport from https://commits.webkit.org/264718@main upstream, authored by Philippe Normand.

Reviewed by Xabier Rodriguez-Calvar.

Don't attempt to gather video rendering metrics if the player hasn't created a video sink.

  • Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamer.cpp: (WebCore::MediaPlayerPrivateGStreamer::updateVideoSinkStatistics):

Canonical link: https://commits.webkit.org/264718@main

…er in error state
This is a backport from https://commits.webkit.org/264718@main upstream.
Reviewed by Xabier Rodriguez-Calvar.
Don't attempt to gather video rendering metrics if the player hasn't created a video sink.
* Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamer.cpp:
(WebCore::MediaPlayerPrivateGStreamer::updateVideoSinkStatistics):
Canonical link: https://commits.webkit.org/264718@main
@eocanha

Copy link
Copy Markdown
Member

IMHO, this kind of trivial backports that don't cause much cherry-pick trouble (don't generate merge conflicts and potential problems) don't even need review. It's fine that you "document" them as a Pull Request, but I think you can even approve and merge it yourself.

@calvariscalvaris left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

As Enrique said, when backporting trivial patches, we don't use reviews.

@cadubentzen
cadubentzen merged commit 42177be into wpe-2.38Aug 21, 2024
@cadubentzen
cadubentzen deleted the wpe-2.38-updateVideoSinkStatistics branch August 21, 2024 07:07
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@cadubentzen@eocanha@calvaris