Our simple solution for this is to prevent recreating the socket
hash table in lookupSocketDescriptor when createIfNotFound is set to
false and exiting with NULL before socketHashTable is called.
OK, I think I have fixed this now in the latest release of the code
(2010.06.11).
--
Ross Finlay
Live-devel] memory leak using tcp
Hi,
i built a RTSP-client with the latest source codes based on the openRTSP-example to receive H.264, MPEG4 and MJPEG-Streams. Using UDP, everything works fine and without memory leaks, but using TCP, there are four small memory leaks as reported earlier by Kami
ail/live-devel/2005-September/003174.html issue I could
not find any answer or solution neither.
Best regards
Alex
__
Od: "Ross Finlayson"
Komu: LIVE555 Streaming Media - development & use
Datum: 11.06.2010 04:31
Předmět:
i built a RTSP-client with the latest source codes based on the
openRTSP-example to receive H.264, MPEG4 and MJPEG-Streams. Using
UDP, everything works fine and without memory leaks, but using TCP,
there are four small memory leaks as reported earlier by Kamil in
the following thread:
http://l
Hi,
i built a RTSP-client with the latest source codes based on the
openRTSP-example to receive H.264, MPEG4 and MJPEG-Streams. Using UDP,
everything works fine and without memory leaks, but using TCP, there are four
small memory leaks as reported earlier by Kamil in the following thread:
http
