Maxim Sharabayko

Hi @amiller-isp Does only the caller-receiver have the memory leak or sender-listener as well?

**A small update.** There seems to be an increase in memory consumption after reconnection of the "caller-receiver". 3.3 MB -> 3.7 MB -> 3.9 MB. During streaming itself memory consumption...

@cg82616424 Thanks for reporting! > SRT Version:1.4.3rc Please define whether RC.0 or RC.1 is used. Or v1.4.3 release.

In the log I see RCV-DROPPED messages starting from seqno %875477239, ``` @869911235:RCV-DROPPED 31 packet(s), packet seqno %875477239 delayed for 556.761 ms ``` while the network capture only has packets...

If you could collect logs and related network captures, that would help diagnose the issue.

Hi @shenlei190810 Do you have any updates on the issue?

### Status Update SRT v1.5.0 The new receiver buffer implementation introduced in SRT v1.5.0 (PR #1964) changes the point when TSBPD base time is being updated. Checking receiver buffer status...

Steady clocks tend to drift. Depends on the hardware, but let's say 200ms an hour. Better to enable the drift tracer. The system clock also drifts, but NTP can compensate...

Core threads synchronization overview. **Note.** `CRcvQueue::m_pRcvUList` may still have this socket, and may be processing it during `releaseSynch()`. Some synchronization is likely required. ### tsbpd() A separate internal thread per...

### TODO - [ ] Make access to `CRcvQueue` thread safe. ```shell Data race aroung CRcvQueue::m_bClosing Write of size 1 at 0x7b4c0000005c by thread T1 (mutexes: write M315, write M312):...