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

Clean up m_RecvLock usage #2304

Open
maxsharabayko opened this issue Apr 21, 2022 · 0 comments
Open

Clean up m_RecvLock usage #2304

maxsharabayko opened this issue Apr 21, 2022 · 0 comments
Labels
[core] Area: Changes in SRT library core Type: Bug Indicates an unexpected problem or unintended behavior
Milestone

Comments

@maxsharabayko
Copy link
Collaborator

The m_RecvLock is intended to synchronize srt_recvmsg2(..) API calls between each other if called from multiple threads, and with the TSBPD thread, in particular, to exchange read-readiness state updates in the blocking mode.

The m_RecvLock mutex is currently used in too many places to protect access to the receiver buffer, where m_RcvBufferLock must be used for that purpose instead.

Epic #1610

@maxsharabayko maxsharabayko added Type: Bug Indicates an unexpected problem or unintended behavior [core] Area: Changes in SRT library core labels Apr 21, 2022
@maxsharabayko maxsharabayko added this to the v1.4.5 milestone Apr 21, 2022
@maxsharabayko maxsharabayko modified the milestones: v1.5.0, Backlog May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[core] Area: Changes in SRT library core Type: Bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant