-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
API: The VmSize of SRS is huge and incorrect, if enabled asan. #4041
Labels
API
HTTP-API, HTTP-Callback, etc.
Bug
It might be a bug.
EnglishNative
This issue is conveyed exclusively in English.
Comments
Get the status of SRS: top -p $(pidof srs)
cat /proc/$(pidof srs)/status
cat /proc/$(pidof srs)/maps
The backtrace with gdb: gdb --args ./objs/srs -c conf/console.conf
|
winlinvip
changed the title
API: The VmSize of SRS is huge and incorrect.
API: The VmSize of SRS is huge and incorrect, if enabled asan.
Apr 24, 2024
Note that I have tried the following actions:
So it is caused by libasan, you can disable asan by After disabled asan: ps -u -p $(pidof srs)
top -p $(pidof srs)
cat /proc/$(pidof srs)/status
cat /proc/$(pidof srs)/maps
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
API
HTTP-API, HTTP-Callback, etc.
Bug
It might be a bug.
EnglishNative
This issue is conveyed exclusively in English.
Describe the bug
When started SRS, the VmSize is huge and incorrect. You can get the VmSize by top or ps.
Version
SRS 5 or 6.
To Reproduce
Steps to reproduce the behavior:
./objs/srs -c conf/console.conf
top -p $(pidof srs)
ps -u -p $(pidof srs)
Expected behavior
Should show correct VmSize.
Screenshots
Additional context
Maybe caused by custom stack for coroutine.
The text was updated successfully, but these errors were encountered: