Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable26] Fix RemoteVideoBlocker still active after removing its associated model #9131

Merged
merged 1 commit into from Mar 22, 2023

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #9125

Once a CallParticipantModel is removed its associated RemoteVideoBlocker
should no longer block the remote video. Otherwise a deferred blocking
would be rejected by the HPB, as the remote peer is no longer available
or, even worse, it could be accepted and block the video of the remote
peer if it joined again since the original model was removed.

To solve that now the RemoteVideoBlocker is destroyed once its
associated model is removed, which causes the RemoteVideoBlocker to
ignore any further call on its methods. Note that the RemoteVideoBlocker
reference can not be nullified instead on the shared datas, as other
components, like the VideoView, expect a RemoteVideoBlocker to be always
available in its shared data. Internally ignoring further calls also
makes the code more robust than just externally guarding any possible
call.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@nickvergessen nickvergessen merged commit 95aea32 into stable26 Mar 22, 2023
18 checks passed
@nickvergessen nickvergessen deleted the backport/9125/stable26 branch March 22, 2023 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feature: call 📹 Voice and video calls feature: frontend 🖌️ "Web UI" client
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants