I’ve been communicating with Martin outside this mailing list to try to track
down what might be going on here.
I’ve concluded for now that this is a ‘false alarm’, and not an error (at
least, not an error in the LIVE555 code).
However, should anyone find a specific problem in the LIVE555 code
> On Jun 15, 2023, at 12:02 PM, Flavio Alves
> wrote:
>
> Hi Ross,
>
> Thank you for your advice. It worked.
>
> I was unable to change the camera settings. I needed to increase the maxSize
> value. As it is a point to point communication, it worked perfectly.
Yes, but - once again - it re
Hi Ross,
Thank you for your advice. It worked.
I was unable to change the camera settings. I needed to increase the
maxSize value. As it is a point to point communication, it worked perfectly.
Best regards,
Flavio
On Wed, 14 Jun 2023 at 18:03, Ross Finlayson wrote:
>
>
> > On Jun 14, 2023,
Hi Mr. Finlayson,
I forgot to update the bug-report.txt and did not test the container
fully That is a mistake on my side. Sending a fixed zip archive.
For the bug, it is a bit difficult to reproduce - that is true.
Best regards,
Martin Mirchev
<>
___
> On Jun 15, 2023, at 1:22 AM, Martin Mirchev wrote:
>
> Hello Mr. Finlayson,
> We still observe the stack-use-after-return bug in live.2023.06.14 while
> running in Ubuntu:20.04.
Sorry, but I wasn’t able to reproduce this (streaming any of "client-request-1”
through "client-request-5”).
Hello Mr. Finlayson,
We still observe the stack-use-after-return bug in live.2023.06.14 while
running in Ubuntu:20.04.
You can reproduce this bug as the README in the attachment as follows:
1. build the docker image:
docker build . -t suaf
2. create the docker container:
docker run -it
