Re: [Live-devel] Invalid read in HandleCmd_DESCRIBE

Hi Mr. Finlayson, https://drive.google.com/file/d/1quP_2ZYA1metNSxyM4xSlSqkF2OWSykY/view?usp=sharing I am sending you link to a docker container, containing the aforementioned crashing version, where the bug

Re: [Live-devel] Invalid read in HandleCmd_DESCRIBE

> On Jun 8, 2023, at 9:24 PM, Meng Ruijie wrote: > > We used the address sanitizer to reproduce this bug again. The following is > the bug report. We also attached the relevant files, and you can reproduce > this bug based on the README. Thank you for the instructions on how to reproduce the

Re: [Live-devel] Memory leak in handleCmd_PLAY

> 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] Invalid read in HandleCmd_DESCRIBE

> On Jun 8, 2023, at 5:08 PM, Meng Ruijie wrote: > > Hi, > > We found one memory issue No you didn’t. You ran “valgrind”, and it said that there was an “invalid read”. But you didn’t find out whether or not this report was real (“valgrind” is often mistaken), and, even if it is real, what

Re: [Live-devel] Memory leak in handleCmd_PLAY

> 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] Invalid read in HandleCmd_DESCRIBE

Hi, We found one memory issue about an invalid read in the function handleCmd_DECRIBE in live.2023.05.10. Here is the bug report from the Valgrind: --- ==1744== Invalid read of size 1 ==1744==at 0x483EF46: strlen (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==1

[Live-devel] Memory leak in handleCmd_PLAY

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