Your message dated Wed, 21 Mar 2018 20:22:42 +0000
with message-id <b769d5dd-3812-131f-4131-f71448c36...@jcowgill.uk>
and subject line Re: Bug#882384: ffmpeg: Gratuitous valgrind log
has caused the Debian Bug report #882384,
regarding ffmpeg: Gratuitous valgrind log
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
882384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 than I
expected.
It's log is attached.
The code for replicating it is in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881777
So,
Kingsley
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages ffmpeg depends on:
ii libavcodec-extra57 7:3.4-2+b1
ii libavdevice57 7:3.4-2+b1
ii libavfilter6 7:3.4-2+b1
ii libavformat57 7:3.4-2+b1
ii libavresample3 7:3.4-2+b1
ii libavutil55 7:3.4-2+b1
ii libc6 2.25-1
ii libpostproc54 7:3.4-2+b1
ii libsdl2-2.0-0 2.0.7+dfsg1-3
ii libswresample2 7:3.4-2+b1
ii libswscale4 7:3.4-2+b1
ffmpeg recommends no packages.
Versions of packages ffmpeg suggests:
pn ffmpeg-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On 25/11/17 22:00, Kingsley G. Morse Jr. wrote:
> 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.
Seems unlikely to me. In all the cases in your log, it looks like glib
has leaked some memory allocated by a constructor somewhere. I also just
tried running valgrind on a random GNOME application which does not use
ffmpeg (gnome-calculator) and got about 100 leak errors so this seems a
likely cause.
> I just happened to run valgrind, saw ffmpeg stuff,
> and thought I should forward it along.
Thanks anyway. I am going to close this bug because I don't think it
affects ffmpeg, but I expect there are bugs somewhere. It might take
some digging to find the right component.
James
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
