sometimes avidemux 2.6.10 freezes while saving video

[Jan Gruuthuse]

have a gdb session of it, see attachment
_____________________________________________
Avidemux v2.6.10 (329d81e)
_____________________________________________
Compiler: GCC 4.8.4
cmake: 2.8.12.2
Build Target: Linux (x86-64)
User Interface: Qt (4.8.6)
_____________________________________________
Kernel: Linux 3.13.0-55-generic (x86_64) (linux-image-3.13.0-55-generic   3.13.0-55.92)
Distribution: Linux Ubuntu 14.04.2 LTS (Trusty)

Intel Core i7-3770K @ 3.50GHz (4 Cores/8 Threads) with 32 GB ram

Desktop: Unity 7.2.5
Display Server: X Server 1.15.1
Display Driver: NVIDIA 349.16
OpenGL: 4.3.0


OpenGL Vendor: NVIDIA Corporation
OpenGL Renderer: GeForce GTX 960/PCIe/SSE2 2048MB (1227/3600MHz)
OpenGL: 4.5.0 NVIDIA 349.16


vdpauinfo:
---------
API version: 1
NVIDIA VDPAU Driver Shared Library  349.16
_____________________________________________

[ajschult]

If you want useful info from gdb, you'll need to at least get a backtrace

Code Select Expand


(gdb) bt


You might also grab backtraces for all threads

Code Select Expand


(gdb) thread apply all backtrace
(gdb) bt


[Jan Gruuthuse]

Code Select Expand

gdb avidemux3_qt4 2>&1 | tee ~/gdb-avidemux3_qt4.txt

(gdb) handle SIG33 pass nostop noprint
(gdb) set pagination 0
(gdb) thread apply all backtrace
(gdb) run
(gdb) bt

was this the correct order?

[mean]

that one is a crash due to detecting memory corruption

[Jan Gruuthuse]

So this could be anything (driver conflict, software layer issues OS <> desktop <> QT4 , ....)
wrong configuration, perhaps hardware issue.
No way to find out exactly?

[Jan Gruuthuse]

vdpau related: Decode or Display. When on xvideo and no HW Accel, avidemux 2.6.10 works fine.

[ajschult]

It's pretty deep into UI code (avidemux, qt, glib) when it crashes.  It will probably be difficult to track down, but you might be able to get more information from valgrind.

valgrind avidemux3_qt4

or

valgrind --log-file=valgrind.log avidemux3_qt4

avidemux (and everything else) runs super-slow under valgrind, so you really want a way to quickly trigger the crash.

[Jan Gruuthuse]

I can not reproduce the issue while running:

Code Select Expand

valgrind --log-file=valgrind.log avidemux3_qt4

If it helps i was able to reproduce the issue while running strace:

Code Select Expand

strace /usr/bin/avidemux3_qt4
Download 447 kB StraceAvidemuxTerminalOutput

[Jan Gruuthuse]

Code Select Expand

valgrind --tool=helgrind --log-file=valgrind.log avidemx3_qt4
was able to produce a log while avidemux halted.
- several lock order "0x... before 0x..." violated showing
- Possible data race during write of size 8