-
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 in videoroom with about 100 viewers after about 1 h #2034
Comments
Nothing we can do with that trace. Please collect more useful info first, and make sure you're on master (there have been fixes last week). |
Check ulimit -a and ulimit -n. By default they are quite low on linux, and janus will crash when it hits a limit. |
Any update on this? Without debugging information there's nothing we can do. I'll interpret lack of feedback as an implicit confirmation this is fixed and I'll simply close. |
Hello,
I will have an opportunity to test it again in production in about 3 weeks.
I will update to the latest version and compile with debug symbols.
I will also check the ulimit value.
In any case I will report the results.
Thank you!
Il giorno mer 8 apr 2020 alle 14:39 Lorenzo Miniero <
notifications@github.com> ha scritto:
… Any update on this? Without debugging information there's nothing we can
do. I'll interpret lack of feedback as an implicit confirmation this is
fixed and I'll simply close.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2034 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB42UVSFDNO7HGFTDT3MEQLRLRWBBANCNFSM4LWTOHWA>
.
|
Please make sure to test whatever will be master, in three weeks, as good chances are we'll have applied fixes in the meanwhile. As a side note, for many viewers the VideoRoom may not be the best option, especially if it's one to many: it may be better to RTP-forward to the Streaming plugin, and use helper threads there. |
Thank you for the information. I will be testing master.
About the VideoRoom for 1-to-many: I have chosen this option because the
publisher can easily transmit the audio-video feed from the browser,
without the need of extra plugins.
In the past I have been using the Streaming plugin, transcoding a RTMP
feed. It used to work.
…On Wed, Apr 8, 2020 at 5:37 PM Lorenzo Miniero ***@***.***> wrote:
Please make sure to test whatever will be master, in three weeks, as good
chances are we'll have applied fixes in the meanwhile. As a side note, for
many viewers the VideoRoom may not be the best option, especially if it's
one to many: it may be better to RTP-forward to the Streaming plugin, and
use helper threads there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2034 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB42UVRZOVPSEJ5VMANOSKTRLSK3TANCNFSM4LWTOHWA>
.
|
Hi guys, I've been experiencing exactly the same issue for several weeks now using the most recent Janus version (tried v0.9.0, v0.9.1 and v0.9.2). Janus crashes as soon as the number of video room participants gets more than 100-120 (hard to say the exact number). I will try to collect more debug info on the next occasion. groupboard: is there any other ulimit value that needs to be bumped other than open files limit (ulimit -n) which indeed is quite low by default (1024 on Debian). I increased it to 10k during the initial setup so at least in my case it's not the issue. |
The only ulimits I had problems with were ulimit -u and ulimit -n. Both were quite low in Centos. |
"Janus crashes" is in no way helpful to us. Please provide what I already asked Lorenzo for. |
One week without info? I don't have a magic wand. Please provide feedback if you need us to fix it, or I'll just close and amen. I won't accept the «I'm busy» card, or I'll have to assume you don't value my time enough. Thanks. |
Hello, please wait until 5 May. A new event is planned on 2/3 May with many
participants. I will test the master version and eventually collect core
dump with debug symbols.
Janus is a great tool and I really appreciate your work.
Il giorno mar 21 apr 2020 alle 10:23 Lorenzo Miniero <
notifications@github.com> ha scritto:
… One week without info? I don't have a magic wand. Please provide feedback
if you need us to fix it, or I'll just close and amen. I won't accept the
«I'm busy» card, or I'll have to assume you don't value my time enough.
Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2034 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB42UVVC4ZGW7FZRH3QG4STRNVJX5ANCNFSM4LWTOHWA>
.
|
Hello guys, sorry for a delayed reply but only today we had an event for such a big number of participants - 140 at its peak. There were several crashes during the event but logs show nothing more than a simple 'Killed' line: https://pastebin.com/ATn3GCAe By using dmesg command I was able to find out why the process was killed by kernel (notice the last two lines) and it was due to the memory leak: In the logs I didn't see any Address Sanitizer information unless I shut down Janus manually while it was working - then I got some extra information: I've also got a GDB backtrace but honestly, it doesn't tell me much: I'm using the most recent version compiled today morning from the master branch. The OS is Ubuntu 18. It's also worth mentioning that most of our events engage less than 100 participants (mostly around 60-80) and there are no issues/crashes reported at all - everything runs smoothly. Any help or advice will be highly appreciated. There is going to be a similiarly crowded event in the upcoming days so I will be surely able to provide more debug information. Thank you. |
Hello, As promised I am providing more information about the issue. I checked out the project on Friday and I built it with debug and AddressSanitizer. Janus crashes randomly with about 100 partecipants. I am adding two consecutive crash logs. |
@lorenzobob0 doesn't look like you're on master, as line numbers don't match. Looks like you're somewhere between |
thanks everyone |
Hello!
Thank you for your excellent work!
I am using Janus to broadcast audio and video from a live event to multiple viewers (1 to many).
Last weekend I was testing it in production with a little less that 100 viewers and I have noticed that after about 1 - 1.5 hours the janus server chrashed. This happenend again multiple times, after about the same time. When the number of viewer decreased (about 50), it did not crash.
I suspect a memory leak.
The stack trace of the debug is here:
https://pastebin.com/RFzfeXk9
Unfortunately the binary was not built with debug symbols.
Please let me know if I can help you find the problem.
Lorenzo
The text was updated successfully, but these errors were encountered: