Closed EvgIL74 closed 4 months ago
xiaozhihong
commented
1 year ago The error is casue by [2023-07-04 19:12:37.704][Error][262728][6tt95789][11] send media data error:code=3041 : demux annexb : annexb start code
You just mentioned when the Larix broadcaster starts to lose packets in any Larix algorithm., Is this error only occurring when the packet is lost?
Can you try to use the develop version and provide the log? Thanks.
EvgIL74
commented
1 year ago You just mentioned when the Larix broadcaster starts to lose packets in any Larix algorithm., Is this error only occurring when the packet is lost? Yes. Its happening when Larix is loosing packets. Can you try to use the developed version and provide the log? I run the developer version (5..0) also, and it was ok. I will provide logs also.
EvgIL74
commented
1 year ago I closed the srt_to_rtmp function in 4.0.228, and now no disconnection is happening, but from now it's a permanent memory leak.
xiaozhihong
commented
1 year ago I closed the srt_to_rtmp function in 4.0.228, and now no disconnection is happening, but from now it's a permanent memory leak.
Version 4.0 srt had unstable and did not provide option srt_to_rtmp, I refactor it in 5.0.
Maybe we can try to resolve this issue #3573, and upgrade your version to 5.x?
EvgIL74
commented
1 year ago Unfortennly, I tried the last 5.X, and the memory leak is happening with the same scenario with Larix.
EvgIL74
commented
1 year ago I think that I figure out the memory leak issue. I checked the 5.0.21 version randomly and found that no memory leak exists on the 5.0.release version. Please look in the previous log and you find out (CasterTsPse)(Invalid ts PSE payload for stream caster) : ts: ts packet decode : ts: demux payload : ts: PES fresh packet length=0, us=0, cc=11 . I think that it's connecting to a memory leak that doesn't exist in 5.0.21 srs.log
winlinvip
commented
1 year ago Version 5.0.21 is outdated; it is recommended to use the latest 5.0 version, such as 5.0.166.
EvgIL74
commented
1 year ago Version 5.0.21 is outdated; it is recommended to use the latest 5.0 version, such as 5.0.166.
As I mentioned in previous remarks. I can't use the latest 5.0 version because it has a huge memory leak in the latest version and I attached a log. Please look at my two previous posts about it.
xiaozhihong
commented
1 year ago Unfortennly, I tried the last 5.X, and the memory leak is happening with the same scenario with Larix.
What is happening with this log? It appears that a certain SRT client is connecting to the server frequently.
xiaozhihong
commented
1 year ago Unfortennly, I tried the last 5.X, and the memory leak is happening with the same scenario with Larix.
I try 5.0.168, no memory leak. Use jemalloc and enable perf_leak, publish srt stream and limit the network to simulate packet loss, try several times, the result shows that no memory leak.
I am puzzled as to why I cannot reproduce this issue in my environment.
You can try streaming for an extended period, such as 30 minutes, and observe that the memory tends to stabilize.
EvgIL74
commented
1 year ago Did you see (CasterTsPse)(Invalid ts PSE payload for stream caster) : ts: ts packet decode : ts: demux payload : ts: PES fresh packet length=0, us=0, cc=11 in your test? I think that it is connected to a memory leak.
Best, Evgeni
xiaozhihong
commented
1 year ago Did you see (CasterTsPse)(Invalid ts PSE payload for stream caster) : ts: ts packet decode : ts: demux payload : ts: PES fresh packet length=0, us=0, cc=11 in your test? I think that it is connected to a memory leak.
Best, Evgeni
Yes, I simulate a 10% loss of my network,
(CasterTsPse)(Invalid ts PSE payload for stream caster) : ts: ts packet decode : ts: demux payload : ts: PES fresh packet length=0, us=0, cc=11 This log appears very frequently.
But still no memory leak.
winlinvip
commented
4 months ago I need to close this issue for disconnecting issue has been fixed in SRS 5.0. However, you can reopen it by reproducing the memory leaking issue.
Description
SRT server in version 4.0.228 disconnects the client immediately(not considered - connection timeout parameter) when the Larix broadcaster starts to lose packets in any Larix algorithm. I tried 5.0.b1, and the issue doesn't repeat at all. I can't use 5.0.b1 because the 5.0.b1 has performance and memory issue that it was reported 3 weeks ago. https://github.com/ossrs/srs/issues/3573
SRS Version: 4.0.228
SRS Log:
SRS Config:
http_api {
whether http api is enabled.
}
http_server { enabled on; listen 8080; dir /mnt/hls; }
srt_server { enabled on; listen 9401; maxbw 1000000000; connect_timeout 4000; peerlatency 2500; recvlatency 2500; latency 2500; }
rtc_server { enabled on;
Listen at udp://8000
}
@doc https://github.com/ossrs/srs/issues/1147#issuecomment-577607026
vhost defaultVhost { min_latency off; tcp_nodelay off; time_jitter off; mix_correct off;
}