Sebastian Dröge wrote:
Am Dienstag, den 02.05.2006, 12:10 +0200 schrieb Eugen Dedu:
Package: thoggen
Version: 0.4.2-2
Severity: important
Thank you for the previous two resolved bugs.
Now, the last bug :o) on my machine:
I start thoggen, I choose File->OpenFolder, choose the directory, the
title appears in the box, choose Ok, the output file configuration
window appears. Now, I choose 720x480. When I press Ok, the progress
window appears, and a few seconds later, thoggen crashes. Here are
the last lines of the output:
:: New video bitrate: 885 kbps (for target size 695.0M)
:: default_aid = 0
:: [1] Selected Audio Stream: en (aid = 0)
:: New video bitrate: 885 kbps (for target size 695.0M)
:: Probing dvddemux audio and video pads ...
:: dvddemux::new-pad 'video_00' (using)
:: dvddemux::new-pad 'audio_00' (using) (mad) (audio/mpeg)
:: Found pads after 1 pipeline iterations.
:: Size 6 = 720x480
:: Using target video bitrate of 885.
:: Saving fatal log mask.
:: Unhandled state change from PLAYING to READY
:: YuvScale: using generic pixops_process() for scaling to 1.000
:: Unhandled state change from PLAYING to READY
:: pixel-aspect-ratio = 16/15 = 1.067
:: YuvScale: using generic pixops_process() for scaling to 1.000
:: Restoring saved fatal log mask.
*** glibc detected *** double free or corruption (out): 0x341ed008 ***
Aborted
I have executed the program twice, the same error appears, and the
same memory address is reported bu glibc.
The third time I executed thoggen, another bug appeared, but I create
another bug for this one.
Hi,
could you please run thoggen in gdb and valgrind, reproduce the crash
and attach the output to this bug?
for gdb use:
gdb thoggen
run
[wait for the double free to happen]
backtrace
for valgrind just run it with:
valgrind --log-file-exactly=valgrind.log thoggen
and attach valgrind.log to this bug
Hi,
I put the two files at http://lifc.univ-fcomte.fr/~dedu/thoggen
For valgrind: I had to stop it with ctrl-c and ctrl-/, because it wasn't
doing anything and ps ux was printing:
root 2568 0.1 0.0 0 0 ? S 22:32 0:04 [pdflush]
dedu 2639 49.3 0.0 0 0 pts/0 Zl+ 22:49 17:49 [mem]
<defunct>
I hope this information is useful.
What's interesting is that with valgrind thoggen started to print
elapsed time in the window, and the .ogg output file has 37kB (without
valgrind, I would had 0 bytes).
Friendly,
--
Eugen Dedu
