< Previous by Date Date Index Next by Date >
  Thread Index  

[reSIProcate-users] Is there any resource leak?


Hello,

Everytime I run reTurn/client/test/TestAsyncClient.cxx, I can see the relay port number keeps increasing. See the 49188 and 49190 in the examples below. I am wondering if there is any resource leak, ie, Turn server still keeps old connection with Turn client? But I can see that mTurnAsyncSocket->destroyAllocation() and mTurnAsyncSocket->close() all have been called. 

#./TestAsyncClient 10.113.54.60 3478 192.168.1.61
. . . . 
MyTurnAsyncSocketHandler::onAllocationSuccess: socketDest=10, reflexive=[UDP 10.113.54.62:6250], relay=[UDP 0.0.0.0:49188], lifetime=600, bandwidth=0, reservationToken=49189
. . . .
CLIENT: destroyAllocation() called
MyTurnAsyncSocketHandler::onReceiveSuccess Done
MyTurnAsyncSocketHandler::onRefreshSuccess: socketDest=6, lifetime=0
MyTurnAsyncSocketHandler::onReceiveFailure: socketDest=4294967295 error=125(Operation aborted.).

#./TestAsyncClient 10.113.54.60 3478 192.168.1.61
. . . .
MyTurnAsyncSocketHandler::onAllocationSuccess: socketDest=6, reflexive=[UDP 10.113.54.62:6250], relay=[UDP 0.0.0.0:49190], lifetime=600, bandwidth=0, reservationToken=49191
. . . .
CLIENT: destroyAllocation() called
MyTurnAsyncSocketHandler::onReceiveSuccess Done
MyTurnAsyncSocketHandler::onRefreshSuccess: socketDest=6, lifetime=0
MyTurnAsyncSocketHandler::onReceiveFailure: socketDest=4294967295 error=125(Operation aborted.).


Tom