JVB Fatal error (more than 200 simltaneous participants)

Hello everyone,

My servers have reached more than 200 simultaneous participants for the first time but JVB couldn’t handle it. I got the following JAVA error ( full log file here) :

# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00007f74608066ff, pid=34804, tid=0x00007f7421626700
# JRE version: OpenJDK Runtime Environment (8.0_232-b09) (build 1.8.0_232-8u232-b09-1~deb9u1-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.232-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libc.so.6+0x15c6ff]
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Although I have a powerful server (see config below), the crash happened before even reaching 10% of CPU usage.

Here’s my config :

  • RAM : 65 GB
  • CPU : Intel® Xeon® Processor E5-2650 v4
  • OS : Debian Buster
  • JVB version : jitsi-videobridge_1126-1_amd64
  • I also have the following lines in /etc/systemd/system.conf :

Any ideas how to improve this ?

Upgrade to jvb 2.1, switch from sctp to web sockets.


Not sure where is the source of this error, in the past we had seen datachannel crashes … currently we are using websockets instead of datachannels …
Any ideas @bbaldino @Boris_Grozev ?
I would say use jvb2

Thanks @damencho
I’m still experiecing the same problem with jitsi-videobridge_1126-1_amd64
I have 2 JVBs and once one of them reaches around 200-300 participants it crashes…

is there any solution without updating to jvb2 ?