> It built and ran first time. Now for the other issue, the one that is “my
> fault”. I am not sure how to fix that issue. my shutdown() function calls
> medium::close(). This is where the first crash was noticed in onReceive that
> you fixed. But it also calls MediaLookupTable::remove and that
ns.live555.com] On Behalf Of Ross Finlayson
Sent: Sunday, November 20, 2011 5:04 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Access violation crash in rtspclient
FYI, I have now released a new version (2011.11.20) of the "LIVE555 Streaming
Media" c
FYI, I have now released a new version (2011.11.20) of the "LIVE555 Streaming
Media" code that should fix this problem.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.liv
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Saturday, November 19, 2011 2:51 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Access violation crash in rtspclient
2 adjustments to the lib
> 2 adjustments to the library allow me to tiptoe thru the call stack avoiding
> accessing destroyed or already deleted members and unwind this stack.
I'll be doing something similar to your first fix (but it most certainly will
not be using a "goto" :-)
> This gest me almost all the way out o
-boun...@ns.live555.com]<mailto:[mailto:live-devel-boun...@ns.live555.com]>
On Behalf Of Ross Finlayson
Sent: Saturday, November 19, 2011 2:11 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Access violation crash in rtspclient
The bye handler calls code result
OK, I see what you're saying now. Yes, you're correct: There is a problem if
the RTCP "BYE" handler - called from within
"RTCPInstance::incomingReportHandler1()" - happens to delete the "RTCPInstance"
object, because we'll continue to execute the rest of the
"incomingReportHandler1()" member
vember 19, 2011 2:11 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Access violation crash in rtspclient
The bye handler calls code resulting in Medium::Close. This ends up calling the
destructor on the RTCP class and deletes the fKnowMembers.
Yes.
The OnRec
> The bye handler calls code resulting in Medium::Close. This ends up calling
> the destructor on the RTCP class and deletes the fKnowMembers.
Yes.
> The OnReceive is then attempted to be called
No, that shouldn't be happening, because the "RTCPInstance" destructor called
"stopNetworkReading(
2011 11:04 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Access violation crash in rtspclient
Following your suggestion I got the Bye handlers working better. But I am back
to a situation that may indicate I am doing to much in my handler.
The case in incoming
appreciate it!
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Wednesday, November 16, 2011 6:15 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Access violation crash in rtspclient
While waiting f
> While waiting for a reply I updated to 11/8/2011. The problem is exactly the
> same.
> I am however still using the async interface, the re-write would kill me
> right now.
Do you mean "still using the *synchronous* interface" (i.e., the old,
now-deprecated interface)? But in any case, that'
e invalid.
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Wednesday, November 16, 2011 4:24 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Access violation crash in rtspclient
I am on 3/14/20
> I am on 3/14/2011 version of live555
Sorry, but no support is given for old versions of the code.
Please upgrade to the latest version. It contains many bugfixes since
3/14/2011, and might (or might not) end up fixing your problem.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
I have been using the live555 client in our project for about a year and it has
been working great for most devices.
I just got a new device that does something wrong and causes a crash of the
entire app. Since it handles multiple cameras this is a real problem.
It is a 4 channel h264 encoder and
15 matches
Mail list logo
