FS#28148 - [libva] h264encode -o file not work

Attached to Project: Arch Linux
Opened by Artem A Klevtsov (unikum) - Saturday, 28 January 2012, 20:07 GMT
Last edited by Allan McRae (Allan) - Saturday, 17 November 2012, 06:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

h264encode aborted when I try use it.
Output example:
h264encode -o 2012-01-01-22\:16\:04.mp4
libva: VA-API version 0.32.0
Xlib: extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva: va_openDriver() returns 0
h264encode: h264encode_common.c:372: main: Assertion `0' failed.
Аварийный останов

Additional info:
* package version(s)
extra/libva 1.0.15-1
extra/vdpau-video 0.7.3-2
extra/nvidia 290.10-2
core/glibc 2.15-4
* config and/or log files etc.
gdb output:
(gdb) r -o test.mp4
Starting program: /usr/bin/h264encode -o test.mp4
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
libva: VA-API version 0.32.0
Xlib: extension "XFree86-DRI" missing on display ":0.0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva: va_openDriver() returns 0
h264encode: h264encode_common.c:372: main: Assertion `0' failed.

Program received signal SIGABRT, Aborted.
0x00007ffff7853935 in raise () from /lib/libc.so.6
(gdb) bt
#0 0x00007ffff7853935 in raise () from /lib/libc.so.6
#1 0x00007ffff7854dab in abort () from /lib/libc.so.6
#2 0x00007ffff784c98e in __assert_fail_base () from /lib/libc.so.6
#3 0x00007ffff784ca32 in __assert_fail () from /lib/libc.so.6
#4 0x000000000040164a in ?? ()
#5 0x00007ffff784038d in __libc_start_main () from /lib/libc.so.6
#6 0x0000000000402a2d in ?? ()
#7 0x00007fffffffe528 in ?? ()
#8 0x00000000ffffffff in ?? ()
#9 0x0000000000000003 in ?? ()
#10 0x00007fffffffe861 in ?? ()
#11 0x00007fffffffe875 in ?? ()
#12 0x00007fffffffe878 in ?? ()
#13 0x0000000000000000 in ?? ()

Steps to reproduce:
$ h264encode -o video-file

Also I note that vlc with hardware acceleration enebled crash on a some h264 encoded files with libva segfault (may be it's related).
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 17 November 2012, 06:50 GMT
Reason for closing:  No response
Comment by Ionut Biru (wonder) - Saturday, 28 January 2012, 20:52 GMT
what video card?
Comment by Artem A Klevtsov (unikum) - Saturday, 28 January 2012, 22:20 GMT
01:00.0 VGA compatible controller: nVidia Corporation GF106 [GeForce 450 GTS] (rev a1)
Comment by Ionut Biru (wonder) - Saturday, 28 January 2012, 23:18 GMT
you need to get a better trace and report upstream.

recompile libva and vdpau-video with debug symbols
https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#One_package_settings_only
Comment by Artem A Klevtsov (unikum) - Saturday, 28 January 2012, 23:37 GMT
After recompile libva and bdpau-video with strip option and $CFLAGS -g -O1 backtrace become short:
(gdb) bt
#0 0x0000003fb6234935 in ?? ()
#1 0x0000003fb6235dab in ?? ()
#2 0x0000000000402d7e in ?? ()
#3 0x0000003fb635db46 in ?? ()
#4 0x0000000000000000 in ?? ()
I get strace output - http://privatepaste.com/3f2d06828b
Comment by Artem A Klevtsov (unikum) - Saturday, 28 January 2012, 23:48 GMT
Sorry, bt is incorrect (my mistake is enable upx). Right output:
(gdb) bt
#0 0x0000003fb6234935 in raise () from /lib/libc.so.6
#1 0x0000003fb6235dab in abort () from /lib/libc.so.6
#2 0x0000003fb622d98e in __assert_fail_base () from /lib/libc.so.6
#3 0x0000003fb622da32 in __assert_fail () from /lib/libc.so.6
#4 0x000000000040179c in main (argc=3, argv=0x7fffffffe528) at h264encode_common.c:372
Comment by Artem A Klevtsov (unikum) - Wednesday, 01 February 2012, 11:22 GMT
What about my problem? I not sure, that I can create correct a bug report to upstream.
Comment by Greg (dolby) - Monday, 15 October 2012, 09:23 GMT
Is this still a problem?

Loading...