[Live-devel] [live-devel] memory leak using scheduledelayedtask
Ross Finlayson
finlayson at live555.com
Mon May 11 23:36:57 PDT 2020
Once again, you’re going to have to figure this out yourself.
In particular, you should check:
- What happens if you use the unmodified “LIVE555 Proxy Server” code?
- What happens if your application contains only the code that you’ve shown below (without *any* “LIVE555 Proxy Server” code)?
- What happens if your “dummytask()” code does nothing at all (except call “scheduleDelayedTask())?
> On May 12, 2020, at 6:01 PM, Siddhant Agarwal <siddhant.agarwal at staqu.com> wrote:
>
> Hi,
>
> I am using scheduleDelayedTask to execute a function dummytask repeatedly.
> Code:
> void dummytask()
> {
> .
> .
> .
> env->taskScheduler().scheduleDelayedTask(uSecsToDelay,
> (TaskFunc*)dummyTask, NULL);
> }
> int main()
> {
> .
> .
> .
> dummytask();
> env->taskScheduler().doEventLoop();
> }
>
> I am getting a memory leak in my code. Where am I doing wrong ?
> I am using live555 proxyserver with rtsp over tcp (-t) option.
>
> Regards,
> Siddhant Agarwal
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
More information about the live-devel
mailing list