acidburn0zzz / webm

Automatically exported from code.google.com/p/webm
1 stars 0 forks source link

Decoder segmentation fault #667

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
vp9    - WebM Project VP9 Decoder v1.2.0-5126-g9e1e7be

Stream is using up/down scaling in all frames. After frame 16 decoder crashes.

./vpxdec --i420 --progress -o dec_%2_%wx%h.yuv stream.vp9
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/grte/v3/lib64/libthread_db.so.1".
16 decoded frames/16 showed frames in 81347 us (196.69 fps)
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7580767 in _int_free (av=0x7ffff78ba720 <main_arena>, p=0x85a520, 
have_lock=0) at malloc.c:4117
4117    malloc.c: No such file or directory.
(gdb) info stack
#0  0x00007ffff7580767 in _int_free (av=0x7ffff78ba720 <main_arena>, 
p=0x85a520, have_lock=0) at malloc.c:4117
#1  0x0000000000443e22 in vp9_resize_frame_buffers (cm=0x7cda50, 
width=<optimized out>, height=<optimized out>) at 
vp9/common/vp9_alloccommon.c:98
#2  0x000000000049c61d in apply_frame_size (pbi=0x7cd820, width=199, 
height=236) at vp9/decoder/vp9_decodeframe.c:716
#3  0x00000000004a5af4 in setup_frame_size_with_refs (rb=<optimized out>, 
pbi=<optimized out>) at vp9/decoder/vp9_decodeframe.c:763
#4  read_uncompressed_header (rb=0x7fffffffb6c0, pbi=0x7cd820) at 
vp9/decoder/vp9_decodeframe.c:1153
#5  vp9_decode_frame (pbi=0x7cd820, p_data_end=0x7fffffffb8b0) at 
vp9/decoder/vp9_decodeframe.c:1299
#6  0x000000000041522c in vp9_receive_compressed_data (ptr=0x7cd820, 
size=<optimized out>, psource=0x7fffffffb8b0, time_stamp=0) at 
vp9/decoder/vp9_onyxd_if.c:348
#7  0x0000000000413e4a in decode_one (deadline=0, user_priv=0x0, data_sz=11264, 
data=0x7fffffffb8b0, ctx=0x7c1290) at vp9/vp9_dx_iface.c:349
#8  vp9_decode (ctx=0x7c1290, data=0x7c1490 "\207\001\004 
\001\214\001\327\001Q\001\021\300\037\004\203\203\r\003", data_sz=11264, 
user_priv=0x0, deadline=0) at vp9/vp9_dx_iface.c:443
#9  0x000000000040dbe6 in vpx_codec_decode (ctx=0x7fffffffba10, data=<optimized 
out>, data_sz=<optimized out>, user_priv=<optimized out>, deadline=<optimized 
out>)
    at vpx/src/vpx_decoder.c:127
#10 0x000000000040c7bd in main_loop (argc=<optimized out>, argv_=<optimized 
out>) at vpxdec.c:898
#11 0x0000000000401a72 in main (argc=6, argv_=0x7fffffffde48) at vpxdec.c:1067

Original issue reported on code.google.com by attilan...@google.com on 20 Nov 2013 at 8:05

GoogleCodeExporter commented 9 years ago

Original comment by attilan...@google.com on 20 Nov 2013 at 8:08

Attachments:

GoogleCodeExporter commented 9 years ago
bisect brings this to: https://gerrit.chromium.org/gerrit/#/c/67830/
expected md5: 1acab5ca2872dac2e273223b2e8f31b3

Original comment by johannko...@google.com on 20 Nov 2013 at 6:46

GoogleCodeExporter commented 9 years ago
This issue should be fixed by the following patch:
https://gerrit.chromium.org/gerrit/#/c/67909/

In the case of odd-sized frames the chroma border was being extended one line 
too far.

Original comment by agra...@google.com on 22 Nov 2013 at 5:29