Closed GoogleCodeExporter closed 9 years ago
Note: the crash occurs here:
_vp8_sad16x16_neon:
vp8_sad16x16_neon: @
@ @
vld1.8 {q0}, [r0], r1
vld1.8 {q4}, [r2], r3 ## BAD ACCESS
vld1.8 {q1}, [r0], r1
vld1.8 {q5}, [r2], r3
Original comment by gbi.linp...@gmail.com
on 19 Mar 2014 at 11:19
I tried on the head of today, and the bug is present as well.
Also, compiling with "-O0 -fno-strict-aliasing" will result in a very slow but
working codec.
Original comment by gbi.linp...@gmail.com
on 21 Mar 2014 at 3:38
This is a dup of https://code.google.com/p/webrtc/issues/detail?id=3038 (see
comment #23 there for a workaround).
Original comment by fischman@chromium.org
on 31 Mar 2014 at 5:52
Original comment by renganat...@google.com
on 3 Apr 2014 at 10:21
I tried the workaround, and it seems to fix it for a simple usage pattern, with
"-O1 -fno-strinct-aliasing" in extra CFLAGS.
But in my experience, it will still fail when we rotate the video within our
app (Linphone).
Internally, I believe we start a new instance of the encoder, but I'll have to
verify.
In any case, the crash seems to occur at the same place.
Original comment by gbi.linp...@gmail.com
on 4 Apr 2014 at 6:49
Here is the fix:
http://git.chromium.org/gitweb/?p=webm/libvpx.git;a=commit;h=33df6d1fc1d268b4901
b74b4141f83594266f041
Original comment by yunqingw...@google.com
on 29 Apr 2014 at 10:05
Original comment by yunqingw...@google.com
on 2 May 2014 at 1:06
Original issue reported on code.google.com by
gbi.linp...@gmail.com
on 19 Mar 2014 at 11:18