Closed Eternal21 closed 8 years ago
Yes, this only occurs when compiled in debug mode with specific flags - check the project properties page in Visual Studio to turn it off. You can ignore it in normal running, it's something we would look at if we were investigating memory leaks. It does have false positives.
Just get rid of those two first compiler flags. If we're pummelling it with load, and we see a lot of those then we might have an issue, usually you'll only see them very occasionally.
Got it. Thanks.
I'm slowly getting up to speed using the library. During some initial testing, I've come across the following error message, which happens to pop up quite often:
Is it a known issue? I was basically hanging up a SIP call using the following socket message:
await _socket.Hangup(_callUuid);
The hangup worked, but I did get those potential leak warnings. Here's the complete log: