-
Notifications
You must be signed in to change notification settings - Fork 266
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
fix(snownet): don't nominate discarded candidates #4806
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Terraform Cloud Plan Output
|
Performance Test ResultsTCP
UDP
|
Updating with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to work. It was hard to reproduce the bug before -- It wasn't reliably reproducible by going from Ethernet -> WiFi -> Ethernet.
Did some testing today and haven't been able to cause the panic.
After some more testing it looks like this is causing #4826 |
When candidates are being invalidated in str0m, they internally set a
discarded
flag. This flag was not considered when a candidate that was previously discarded was added again. This can happen when a client roams back to their old network, i.e. going from Ethernet to WiFi and back.In that case, str0m would still form new pairs using the old discarded candidate which would also eventually get nominated as part of a pair. This would lead to a panic in snownet when we try to find the nominated local candidate as we filter by non-discarded candidates there.
Related: algesten/str0m#508.
Resolves: #4736.