Thanks for the report.
This (tiny) memory leak can be fixed by changing line 190 of
"liveMedia/RTPInterface.cpp" from
SocketDescriptor* socketDescriptor = lookupSocketDescriptor(env,
socketNum);
to
SocketDescriptor* socketDescriptor = lookupSocketDescriptor(env,
socketNum, False
Hi Ross
> No you don't :-)
I’m happy to be wrong on that.
> No, I can't do that, because if that code happens to be called while we're
> inside "tcpReadHandler1()" - i.e., while we're inside this loop:
Thanks for taking a look and fixing it. I did notice the crash of course. I
sent my messa
> I know your stance on memory leaks
No you don't :-)
> In the SocketDescriptor destructor, the HashTable::Iterator* “iter” is never
> deleted.
Yes - that was an oversight on my part. It will be fixed in the next release
of the software.
> In SocketDescriptor::deregisterRTPInterface, the f
Hi All,
Please ignore the previous patch I sent with the same subject line; I hit
Send too soon. My apologies for the spam.
Thanks,
Chris Richardson
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/list
RESTRICTED@@]
De : live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] De la part de Ross Finlayson
Envoyé : mardi 13 décembre 2011 15:06
À : LIVE555 Streaming Media - development & use
Objet : Re: [Live-devel] memory leaks in DelayQueue ?
I continue to analyse memory l
> I continue to analyse memory leaks
Yes, but you should do so on an up-to-date version of the code!
> In BasicUsageEnvironment/DelayQueue.cpp
>
> DelayQueue::~DelayQueue() {
> - while (fNext != this) removeEntry(fNext);
> + while (fNext != this) { DelayQueueEntry* entry=fNext; removeEntr
I searched all files of live555, found nowhere to delete the pointer
of BasicTaskScheduler instance, include playcommon.c . I don't know
whether I should delete it myself.
But the destructor of class "BasicUsageEnvironment" is declared in
protected field and cannot accessed by "delete". Should I
See my previous message to the list.
(And *do not* send the same message to the list multiple times!)
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailma
I am sending the file which describes regarding the
memory leak in the code.
I'm not convinced that any of these are real memory leaks; instead,
they seem to just be the "LIVE555 Media Server" doing its job.
Note that the server works by dynamically allocating a
"ServerMediaSes
There are few memory leaks in
liveMedia/OnDemandServerMediaSubsession.cpp, the object(inputSource)
created is not freed.
No, that's not true. The input source for each
"ServerMediaSubsession" is freed by the "CloseStreamSource()"
function, which in turn is called by "StreamSta
Eyal,
Thanks for the report. These fixes will be included in the next
release of the software.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/lis
11 matches
Mail list logo
