-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Crash for unknown reasons #2300
Comments
Clearly not master, as line numbers don't match. As clearly explained in the guidelines, you have to try master first, or we won't look at the issue. |
Looks like a race condition where both sides are closed more or less at the same time: this commit a6731ba should help address it. Closing for the time being, let us know if it's still not fixed. |
The problem remains, |
I wouldn't say "the problem remains", since it happens in a completely different place, which means the original issue has been solved. Busy now, I'll try to find time later or in the next few days. |
OK, I'm careless。 |
Mh, looks like it's a similar issue: the peer is freed while we're using its structure. I guess we're missing sessions referencing each other when they're in a call to each other (or trying to establish a call), which might help prevent this. I'll try to work on a fix and let you know when there's a commit to try. |
Please check the above commit, to see if it fixes it for you. |
The crash took place further forward,The content is relatively small, I posted it directly
|
My fault, there was a copy/paste typo: ef954f9 should fix it. |
@648540858 any update? Can this be closed? |
I've been testing it for a day and it hasn't happened again. It's great |
this is the log;
https://gist.github.com/648540858/44135642522fe4fdb6f15865581c4c9a
I added the field displayName. The modified file is in the log。I'm not sure that's what caused it。
The text was updated successfully, but these errors were encountered: