: Wednesday, September 23, 2009 5:35 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] H264FUAFragmenter glibc error
>At a quick glace it seems to really only be set to 6, in the source
>code.
Yes, but note that it's a *variable*. You can change it yoursel
At a quick glace it seems to really only be set to 6, in the source
code.
Yes, but note that it's a *variable*. You can change it yourself, in
your own code.
Thanks again for your input, I will modify the value used to create the
H264FUAFragmenter() object.
No! You don't need to chan
ment & use
Subject: Re: [Live-devel] H264FUAFragmenter glibc error
>Was there any reason the
>fInputBufferSize is set to OutPacketBuffer::maxSize, which is hard
coded
>to 60,000?
It's not 'hard coded'; "OutPacketBuffer::maxSize" is a *variable*.
You may set it y
Was there any reason the
fInputBufferSize is set to OutPacketBuffer::maxSize, which is hard coded
to 60,000?
It's not 'hard coded'; "OutPacketBuffer::maxSize" is a *variable*.
You may set it yourself (e.g., to some larger value), before you
create your "H264VideoRTPSink" object.
--
Ross Finl
rom: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Tuesday, September 22, 2009 6:36 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] H264FUAFragmenter glibc error
>~H264FUAFragmenter()
>fInputBu
~H264FUAFragmenter()
fInputBuffer = 0xfcbb0
*** glibc detected *** ./cap_encode_omap3530.x470MV: double free or corruption
I suspect that "double free" is really the problem. You should check
to make sure that "~H264VideoRTPSink()" isn't being called more than
once on the same object.
You s
I have been using the live555 media library for streaming H.264 encoded
data stream, on an ARM based embedded linux platform. It is working for
the most part, except for Stopping the stream, at which point I get the
following glibc error:
~H264FUAFragmenter()
fInputBuffer = 0xfcbb0
*** glibc
