Hi James,
Yeah, I saw glib and gobject in valgrind's stack
traces too.
I agree ffmpeg may not have a memory bug.
My only doubt?
A dynamic library call might hide one.
I see "dl-init.c" in valgraind's stack traces.
And, I read the following blunt criticism
/* Stupid users forced the ELF s
Hi Carl,
> Nearly all messages seem to relate to melt, not FFmpeg.
Thanks for your informed thoughts.
> Can you reproduce any issues with ffmpeg (the executable)?
>
> The crc issue surprises me a little: Can you produce different
> output files if you use the valgrind option --malloc-fill?
Sur
Package: ffmpeg
Version: 7:3.4-3
Severity: normal
Hey guys,
Thank you very much for maintaining Debian's
ffmpeg package.
It's been an enormous source of fun.
In the course of chasing down a different bug, I
had the opportunity to run "melt" with valgrind.
Valgrind reported more ffmpeg problems
Hi Sebastian,
Thank you very much for sharing your thoughts.
It seems to me you asked a reasonable question:
> Why should frei0r-plugins break itself?
Through no fault of your own, when I filed the bug
report, I
1.) was unaware that a source package named
just "frei0r" existed, an
Package: frei0r-plugins
Version: 1.6.1-1+b1
Severity: minor
Dear Maintainer,
Thanks for maintaining frei0r's plugins.
They look cool.
* What led up to the situation?
I wondered why ffmpeg failed to use frei0r plugins
as ffmpeg sources.
* What exactly did you do (or not do) that was effective
