-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Source: The memory leak seems still exist #4096
Comments
What's your SRS config? |
I use the rtmp2rtc.conf or srs.conf which enable rtmp_to_rtc.
|
I use the version which you merged newest code on morning. |
Memory growth does not necessarily indicate a leak; it could be due to system caching, among other things. You can conduct tests for over an hour, and if the increase persists, then it is likely a leak.
|
The memory issue with SRS still appears to persist. I use RTMP to push streams to SRS, and then play them using WebRTC. After playing for a while, I close the stream, then push and play again, only to close it once more.
Version: 6.0 develop branch 2024.6.18
this is my test result:
unit is KB
Startup memory: SRS 19032.
datetime play 16 streams close all streams
13:58 77624 53152
14:03 79229 79220
14:06 95260 95260
14:13 96260 96260
14:18 97256 97256
14:28 98428 98428
14:35 99500 99500
14:42 100768 100768
14:53 101780 101900
14:59 104476 104476
15:33 107744 107744
TRANS_BY_GPT4
The text was updated successfully, but these errors were encountered: