.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of agrit...@cnord.ru
Sent: Thursday, February 28, 2013 1:58 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] rtsp proxy: memory leak
2013/2/28 Ross Finlayson :
> Unfortunately I can not use valgrind for debuggi
2013/2/28 Ross Finlayson :
> Unfortunately I can not use valgrind for debugging the leak because it
> is not available on the platforms the problem is reproducible on.
>
>
> And what platforms are these? Let me guess - Windows? Sigh...
No, they are are qemu-arm (which emulates armv5) and TI AM33
> Unfortunately I can not use valgrind for debugging the leak because it
> is not available on the platforms the problem is reproducible on.
And what platforms are these? Let me guess - Windows? Sigh...
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
You are right, it is available. I tried to use it but it fails with
disInstr(arm): unhandled instruction: 0xEEBA7BC1
cond=14(0xE) 27:20=235(0xEB) 4:4=0 3:0=1(0x1)
immediately after the log message
"ProxyServerMediaSubsession["H264"]::createNewStreamSource".
--
Anton
2013/2/28 F
Hi Anton,
On 02/28/2013 08:39 AM, agrit...@cnord.ru wrote:
Hello,
I believe I found a huge memory leak in the rtsp proxy server. The
problem is that I can only reliably reproduce it on qemu-arm or
physical armv7 device. It doesn't happen when I run rtsp proxy on my
x86-64 machine. Moreover, it
Hello,
I believe I found a huge memory leak in the rtsp proxy server. The
problem is that I can only reliably reproduce it on qemu-arm or
physical armv7 device. It doesn't happen when I run rtsp proxy on my
x86-64 machine. Moreover, it only reveals when there are four or more
clients connected to
