-
Notifications
You must be signed in to change notification settings - Fork 380
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
rtpengine mr10.5 crashed in __dtx_send_later #1817
Comments
A large timestamp shouldn't be a problem, but the |
ok thank you, here you go:
|
There are many more occurrences that are happening in AMR transcoding scenario (branch mr11.5) due to CN dtx handling.
I will try |
What does |
hi,
attached completed output. |
How about
|
here you go
|
Ok, one more.
|
sure
|
Do you have debug symbols for libavcodec.so.58? There isn't anything obvious wrong on the rtpengine side, so would be interesting to know where exactly ffmpeg crashed. (Also the exact source/version would be important to know) |
Hi thanks,
Dockerfile:
I'll add the |
The version is ffmpeg4 - 4.4.5, in the so filename i can see libavcodec.so.58.134.100 |
It was a 4.4.4 actually but that didn't work |
rtpengine version the issue has been seen with
mr10.5.1
Used distribution and its version
Ubuntu 18.04.6 LTS
Linux kernel version used
No response
CPU architecture issue was seen on (see
uname -m
)x86_64
Expected behaviour you didn't see
No response
Unexpected behaviour you saw
I am seeing a seldom crash, last week two hosts crashed independently.
Steps to reproduce the problem
Not sure, but there's one idea . Am I seeing it right that some endpoint is sending the RTP packet with huge
ts
causing this behavior?Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000055bed2c174a5 in decoder_input_data_ptime (dec=0x7fc6ec17e690, data=0xc0089a793fe274df, ts=4715930405566051902, ptime=ptime@entry=0x7fc7bb5f9288,
callback=0x55bed2bebbe0 <packet_decoded_fifo>, u1=0x7fc73c089d90, u2=0x7fc7bb5f91c0) at codeclib.c:936
Additional program output to the terminal or logs illustrating the issue
something more:
The text was updated successfully, but these errors were encountered: