Skip to content
This repository has been archived by the owner on Jul 12, 2023. It is now read-only.

PlayerEndpoint failure when stopping and starting again #633

Open
3 tasks done
j1elo opened this issue Oct 4, 2022 · 2 comments
Open
3 tasks done

PlayerEndpoint failure when stopping and starting again #633

j1elo opened this issue Oct 4, 2022 · 2 comments
Assignees
Labels
bug Non-critical bug affecting expected behavior

Comments

@j1elo
Copy link
Member

j1elo commented Oct 4, 2022

Prerequisites

These are MANDATORY, otherwise the issue will be automatically closed.

Issue description

PlayerEndpoint shows a frozen frame when calling stop() followed by `play().

Context

OpenVidu support for IP cameras.

How to reproduce?

  1. Create a PlayerEndpoint with a test stream (e.g. an mjpeg or rtsp)
  2. Start playing (play())
  3. Stop playing (stop()). Pausing is not enough, as it keeps the connection active, while we want to save resources and thus all connections should be closed.
  4. Start playing again (play())

Expected & current behavior

Instead of playing again, it shows a frozen frame. Logs show lots of errors pointing to invalid PTS and DTS.

(Optional) Possible solution

Commenting out these two lines the playback restarts successfully. It all points at a potential lack of reinitialization of variables when the stop() is processed. Later, upon the new play(), the expected PTS/DTS don't match the incoming ones, and thus the code exits early. At least that's what it seems to me, after a quick look around.

About Kurento Media Server

  • Kurento version: dev-7.0.0
  • Server OS: Ubuntu 20.04
  • Installation method:
    • [] [apt-get]
    • [] [Docker]
    • [] [AWS CloudFormation]
    • [Built from sources]
@j1elo j1elo self-assigned this Oct 4, 2022
@j1elo j1elo added the bug Non-critical bug affecting expected behavior label Oct 4, 2022
@github-actions
Copy link

github-actions bot commented Oct 4, 2022

Hello @j1elo! 👋 we're sorry you found a bug... so first of all, thank you very much for reporting it.

To know about progress, check in Triage. All issues are considered Backlog Candidates until work priorities align and the issue is selected for development. It will then become part of our official Backlog.

@j1elo
Copy link
Member Author

j1elo commented Oct 4, 2022

Possibly related commit: Kurento/kms-elements@0c0bdd6

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Non-critical bug affecting expected behavior
Projects
None yet
Development

No branches or pull requests

1 participant