Process freezed if WebRTC thread received signal 11 (SIGSEGV) and won't terminate itself
billy-sung opened this issue · 3 comments
billy-sung commented
Describe the bug
if this log is shown, all clients cannot create websocket connection.
To Reproduce
Steps to reproduce the behavior:
- create 4 origin with originMapStore
- create 1 edge with dynamic application
- create 80+ rtmp streams to origin
- view all stream one by one via WebRTC with OvenPlayer
- edge would stop working if
C [AW-WebRTC0:32] OvenMediaEngine | signals.cpp:124 | OME v0.16.8 ((From archive)) received signal 11 (SIGSEGV), interrupt.
printed.
Expected behavior
edge should terminate itself, and let it restart itself
Logs
20240730-edge.log
Please upload the entire OvenMediaEngine.log. You may delete important personal information.
Server (please complete the following information):
- OS: Container-Optimized OS
- OvenMediaEngine Version: v0.16.8
- Branch: master
Player (please complete the following information):
- Device: PC
- OS: Windows 10
- Browser: Chrome
- Version 127
Additional context
(empty)
dimiden commented
@billy-sung
Container-Optimized OS is not officially supported, so I would like to request a few things to analyze this issue.
Dockerfile
file
- We need the
Dockerfile
used to build OME to obtain the non-stripped binary. - Please attach the
Dockerfile
used for the build here.
- Crash Dump file
- A crash dump is needed to trace where the crash occurred.
- Crash dump files are created in
<OME executable>/dumps
, so you can copy them from the running container usingcp
or mount(-v
) that path to external storage to extract the dump files generated when the crash occurs. - Please attach the extracted dump files here.
Server.xml
files
- To reproduce the issue, we need the
Server.xml
files for both Origin and Edge. - Please upload the
Server.xml
files for both Origin and Edge here.
longcurisa commented
when have whep