Re: [Live-devel] Memory leak in handleCmd_PLAY

2023-06-08 Thread Ross Finlayson
> On Jun 8, 2023, at 11:22 PM, Meng Ruijie wrote: > > We now show you where the memory leak happens as follows. We also attached > the reproduction steps, so that you can reproduce this bug based on the > README. > > > > ==2720== 96 bytes in 1 blocks are definitely lost in loss record

Re: [Live-devel] Memory leak in handleCmd_PLAY

2023-06-08 Thread Ross Finlayson
> On Jun 8, 2023, at 5:03 PM, Meng Ruijie wrote: > > Hi, > > We found one memory leak No you didn’t. You ran “valgrind” on an application that uses our RTSP server implementation. At one point in the program, you exited it (presumably by modifying the code). When you exited the program,

[Live-devel] Memory leak in handleCmd_PLAY

2023-06-08 Thread Meng Ruijie
Hi, We found one memory leak in the function handleCmd_PLAY in live.2023.05.10. Here is the bug report from the valgrind: --- ==1755== Invalid read of size 1 ==1755==at 0x483EF46: strlen (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==1755==by 0x4E2FD14: __v