There is also the 'failure' memory leak
Yes, I'll take care of that as well.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
Ross Finlayson wrote:
I agree that WinCE should not be doing that. However, IMHO, requesting
a port over and over, assuming that the OS will eventually give you
something suitable, is a risky behavior
There's really no alternative. We can't just arbitrarily choose an
even number ourselves, in
I agree that WinCE should not be doing that. However, IMHO, requesting
a port over and over, assuming that the OS will eventually give you
something suitable, is a risky behavior
There's really no alternative. We can't just arbitrarily choose an
even number ourselves, in case we get a port num
Hello,
> But if the port was allocated the first time (and recorded in the
> hash table), then your OS should never be allocating it (as an
> ephemeral port) a second time! If your OS really is doing this
> (allocating the same ephemeral port number a second time, while the
> first-allocated
I'd like to report a bug in MediaSubsession::initiate. Windows
CE/Mobile shitty IPstack sometimes seems to always return the same
odd port so initiate() loops and creates sockets until the device
hasn't enough memory.
The Hashtable mechanism won't work as the result
socketHashTable->Add() isn
Hello,
I'd like to report a bug in MediaSubsession::initiate. Windows CE/Mobile
shitty IPstack sometimes seems to always return the same odd port so
initiate() loops and creates sockets until the device hasn't enough memory.
The Hashtable mechanism won't work as the result socketHashTable->Ad
