freeze copy .ts to .ts avidemux 2.6.8

[Jan Gruuthuse]

Freeze
Load this video: 720p4audioTracks3sat (69 MB download link, if you don't have the video)
vdpau encoder
Save to .ts output with copy for both video and audio: avidemux freezes, save to .mkv did work
While running with GDB these did come along

Code Select Expand

[A*** Error in `/usr/bin/avidemux3_qt4': free(): invalid pointer: 0x0000000001d99f10 ***
DM_verifyDts]  Verifying DTS....


Code Select Expand

[Thread 0x7fffa3fff700 (LWP 24712) exited]
[Thread 0x7fffd8cf8700 (LWP 24381) exited]
[Thread 0x7fffa9482700 (LWP 24710) exited]
[Thread 0x7fffa8c81700 (LWP 24711) exited]
[Thread 0x7fffa9d39700 (LWP 24709) exited]
[Thread 0x7fffcffff700 (LWP 24708) exited]
[New Thread 0x7fffcffff700 (LWP 25133)]
[New Thread 0x7fffa9d39700 (LWP 25134)]
[New Thread 0x7fffa8c81700 (LWP 25135)]
[Thread 0x7fffa8c81700 (LWP 25135) exited]
[Thread 0x7fffcffff700 (LWP 25133) exited]
[New Thread 0x7fffcffff700 (LWP 25256)]

Program received signal SIGABRT, Aborted.
0x00007ffff235dcc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
_____________________________________________
Avidemux v2.6.8 (d73b1a8)
_____________________________________________
Compiler: GCC 4.8.2
cmake: 2.8.12.2
Build Target: Linux (x86-64)
User Interface: Qt (4.8.6)
_____________________________________________
Kernel: Linux 3.13.0-44-generic (x86_64) (linux-image-3.13.0-35-generic 3.13.0-35.62)
Distribution: Linux Ubuntu 14.04.1 LTS (Trusty)

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

Desktop: Unity 7.2.3
Display Server: X Server 1.15.1
Display Driver: nouveau  1.0.11
OpenGL: 2.1.2

OpenGL Vendor: NVIDIA Corporation
OpenGL Renderer: GeForce GT 520/PCIe/SSE2 1024MB (810/535MHz)
OpenGL: 4.2.0 NVIDIA 304.125
Compiler: GCC 4.8 + CUDA 5.5

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

[Jan Gruuthuse]

This is very weird?
Doing the test with valgrind again: nothing went wrong.
So test again without valgrind: nothing went wrong
So reboot, test again without valgrind: nothing went wrong
included valgrind log of the session, perhaps it contains useful information.