>> I have now installed a new version (2016.09.05) of the “LIVE555 Streaming
>> Media” code that should, I believe, fix a problem (actually, one error and
>> one warning) that showed up in this log. I hope this helps!
> From my initial tests the Valgring error message seems to have been solved
> But based on your changes and the warning stack-trace I've tested similar
> change in GenericMediaServer::ClientConnection::closeSockets() and the
> valgrind warning is no more.
> See also the changes made bellow.
Thanks. I’ll be including this in the next release of the software.
Ross Finla
> I have now installed a new version (2016.09.05) of the “LIVE555 Streaming
> Media” code that should, I believe, fix a problem (actually, one error and
> one warning) that showed up in this log. I hope this helps!
From my initial tests the Valgring error message seems to have been solved, I
> See valgrind output and RTSPServer debug output in the file attached to this
> message.
Thanks; this helped a lot.
I have now installed a new version (2016.09.05) of the “LIVE555 Streaming
Media” code that should, I believe, fix a problem (actually, one error and one
warning) that showed up
Hi!
Following up this pending discussion:
http://lists.live555.com/pipermail/live-devel/2016-March/019977.html
> Another thing I suggest is running your code under ?valgrind?. If - as I
> suspect - the code is trying to access an object that has recently been
> deleted, then ?valgrind? may be
On Tue, March 15, 2016 00:17, Ross Finlayson wrote:
>
> I suggest looking at the various places - within your own application code -
> where you might be deleting LIVE555 objects (using ?Medium::close()?), and
> make sure that you?re not accidentally deleting them twice, or not deleting
> them when
> - from the core dumps it's hard to tell which action causes the crash since
> it's an asynchronous event but the stack trace is always the same:
> «
> (gdb) bt
> #0 0x636e456c in ?? ()
> #1 0x08091c89 in FramedSource::afterGetting (source=0x8647d50) at
> FramedSource.cpp:91
> #2 0x080d8825 in
Hello Ross,
in http://lists.live555.com/pipermail/live-devel/2013-January/016347.html I
described the following scenario: "We have been running for some time a
RTSPServer that acquires video from a live source (with our own DeviceSource)
from which we create 2 or 3 replicas: one for multicast stre
