There is a known memory leak related to Candidate Pairs (active connections) in the IceLink 3.2.3.666 release. The leak is minor as the rate is ~1KB/s, but that can have a big impact over time and multiple connections. All memory is properly released when connections shut down, so it's not a permanent leak. A patch is going to QA tonight for validation, and we will be releasing another build of 3.2.3 this week to address this issue.
Update
The IceLink 3.2.3.684 release of June 15th, 2018 fixed this issue. The release note is given here:
- Fixed a memory leak regression in IceLink release 3.2.3, where IceTransport was storing unnecessary CandidatePair information associated with ICE KeepAlives and populated CandidatePair statistics with redundant information (IL-1817);
Comments
0 comments
Article is closed for comments.