Core dumped when using ffmpeg2theora on m4v video

Bug #1631505 reported by jfbaillette
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ffmpeg2theora
New
Undecided
Unassigned
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

ffmpeg2theora 0.29

 Xiph.Org libtheora 1.1 20090822 (Thusnelda)
 Xiph.Org libVorbis 1.3.5
 FFmpeg libavcodec 57.48.101
 FFmpeg libavformat 57.41.100

valgrind ffmpeg2theora VIDEO.m4v -o VIDEO.ogv -x 640 -y 360 --videoquality 5 --audioquality 0 --frontend
==4142== Memcheck, a memory error detector
==4142== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==4142== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info
==4142== Command: VIDEO.m4v -o VIDEO.ogv -x 640 -y 360 --videoquality 5 --audioquality 0 --frontend
==4142==
==4142== Invalid write of size 8
==4142== at 0x7C76899: av_samples_fill_arrays (in /usr/lib/x86_64-linux-gnu/libavutil.so.55.28.100)
==4142== by 0x7C76BB8: av_samples_alloc (in /usr/lib/x86_64-linux-gnu/libavutil.so.55.28.100)
==4142== by 0x40ECC1: ??? (in /usr/bin/ffmpeg2theora)
==4142== by 0x40542E: main (in /usr/bin/ffmpeg2theora)
==4142== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==4142==
==4142==
==4142== Process terminating with default action of signal 11 (SIGSEGV)
==4142== Access not within mapped region at address 0x0
==4142== at 0x7C76899: av_samples_fill_arrays (in /usr/lib/x86_64-linux-gnu/libavutil.so.55.28.100)
==4142== by 0x7C76BB8: av_samples_alloc (in /usr/lib/x86_64-linux-gnu/libavutil.so.55.28.100)
==4142== by 0x40ECC1: ??? (in /usr/bin/ffmpeg2theora)
==4142== by 0x40542E: main (in /usr/bin/ffmpeg2theora)
==4142== If you believe this happened as a result of a stack
==4142== overflow in your program's main thread (unlikely but
==4142== possible), you can try to increase the size of the
==4142== main thread stack using the --main-stacksize= flag.
==4142== The main thread stack size used in this run was 8388608.
==4142==
==4142== HEAP SUMMARY:
==4142== in use at exit: 2,955,775 bytes in 2,333 blocks
==4142== total heap usage: 4,328 allocs, 1,995 frees, 21,257,942 bytes allocated
==4142==
==4142== LEAK SUMMARY:
==4142== definitely lost: 0 bytes in 0 blocks
==4142== indirectly lost: 0 bytes in 0 blocks
==4142== possibly lost: 895 bytes in 8 blocks
==4142== still reachable: 2,954,880 bytes in 2,325 blocks
==4142== suppressed: 0 bytes in 0 blocks
==4142== Rerun with --leak-check=full to see details of leaked memory
==4142==
==4142== For counts of detected and suppressed errors, rerun with: -v
==4142== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Erreur de segmentation

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.