-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
WebRTC: AddressSanitizer: heap-use-after-free #3413
Comments
asan's stack is too small, why is there no complete stack? Can you check if there are any other logs available? If not, the only option is to map the core file and check the stack.
|
Last week, I observed for a week but still couldn't find a way to reproduce it. The logs before the crash only have the logs recorded above. How is the core file mapped out?
|
Just to add to the phenomenon of xiangzi1: when playing 27 videos through WebRTC on the browser, there is a continuous increase in memory usage in SRS. Every 30 seconds, it stops and then resumes playing. After running for more than ten hours, it eventually crashes with the error "heap-use-after-free". This issue was discovered in version V5.0.141@winlinvip.
|
SRS Config srs_log_tank console; |
|
During the htp_hook_on_play period, the rtc connection timed out and was deleted, resulting in the use of a wild pointer.
|
@limjoe Please ask a question. I noticed that when you start Docker, SRS logs are printed to the console. I remember that after the container restarts, the logs cannot be found, right? I wonder how you find the logs of previous containers? Do you record the container ID?
|
@winlinvip In k8s, using the command "kubectl logs -f origin-rtmp-cluster-1 --tail=100 -p" allows you to view the logs before the container crashes.
|
@limjoe, can you make this log above more complete? Or you can stop logging to the console and directly output it to a file.
|
Description
v6.0.22 code, after compiling with Docker, it was noticed that certain pods had restart records after running for a while. Upon checking the logs, there were error records indicating heap_buffer_overflow, which is a memory overflow issue.
Docker compilation command
SRS Version: v6.0.22
SRS Log:
Replay
Please describe how to replay the bug?
Step 1: docker image build
Step 2: docker run and push rtmp stream
Expect
No memory overflow crash issue during normal operation.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: