-
Notifications
You must be signed in to change notification settings - Fork 995
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
suspiciously large buffer stack traces #1769
Comments
We keep the stack trace is in the logs because we still don't understand the issue(s). We do drop these packets in the sense that we don't return them back to the memory pool, and we don't remove the user from the conference. This instance is due to a large TCC feedback packet that we generate. Your observation that it correlates with users losing connectivity is interesting -- perhaps the encoding is inefficient when packet loss is high. |
We are experiencing the same issue. This warning is shown multiple times (20+ times over 2 seconds.). Users lose connection or video freezes.
|
I am experience the same issue with jitsi-videobridge2/stable,now 2.1-570-gb802be83-1 |
Might be related with #1703 (comment), happening on 2.1-617-ga8b39c3f-1 for me too. |
I seem to have the same problem, leading to video no longer working
|
Description
We observe on several jitsi videobridges buffer warnings. This is also reported in the community forum e.g. here.
Current behavior
The warnings seem to be related with users being in a state when they are loosing connectivity and finally fall out of the conference. We first investigated if it was related to VPN users only, but also have seen this with other users connected without VPN.
Expected Behavior
Maybe drop large packets, keep user in conference, or do not spill stackTraces in the log if this is a minor warning issue.
Environment details
The text was updated successfully, but these errors were encountered: