[x264-devel] Crash on ARMv7 systems with --preset veryslow and --preset placebo

Stefan Grönroos stefan.gronroos at gmail.com
Sun Mar 3 13:46:18 CET 2013


Hi,

I was also able to reproduce the fault.

Seems like i_src_stride is corrupt when mc_luma is called. The fault seems
to lie in the mc_weight asm functions for NEON, since the attached patch
seems to remove the problem (I'm not suggesting to apply that patch, just
pointing out the problem).
I'll try to look into where exactly things go wrong, if no one suspects
something particular already.

//Stefan

On Sun, Mar 3, 2013 at 8:10 AM, Marat Dukhan <maratek at gmail.com> wrote:

> Program received signal SIGSEGV, Segmentation fault.
> 0x00077694 in x264_pixel_avg2_w8_neon ()
> (gdb) bt
> #0  0x00077694 in x264_pixel_avg2_w8_neon ()
> #1  0x000736d2 in mc_luma_neon (
>     dst=0x13b618 "\320\311\326\335\322\316\330", <incomplete sequence
> \326>,
>     i_dst_stride=32, src=<optimized out>, i_src_stride=<optimized out>,
>     mvx=-327, mvy=151, i_width=8, i_height=8, weight=0x137890)
>     at common/arm/mc-c.c:140
> #2  0x0005f452 in x264_me_refine_qpel_rd (h=0x136600, m=0xbeffaf80,
>     i_lambda2=2925, i4=12, i_list=0) at encoder/me.c:1273
> #3  0x00057288 in x264_macroblock_analyse (h=0x136600)
>     at encoder/analyse.c:3378
> #4  0x00020828 in x264_slice_write (h=0x136600) at encoder/encoder.c:2351
> #5  0x000213fa in x264_slices_write (h=0x136600) at encoder/encoder.c:2667
> #6  0x00024532 in x264_encoder_encode (h=<optimized out>,
> pp_nal=0xbeffed10,
>     pi_nal=0xbeffed14, pic_in=<optimized out>, pic_out=0xbeffec50)
>     at encoder/encoder.c:3273
> #7  0x0000ac88 in encode_frame (h=<optimized out>, hout=0x111008,
>     pic=0xbeffed80, last_dts=0xbeffeef0) at x264.c:1674
> #8  0x0000c222 in encode (opt=0xbeffeeb8, param=0xbeffef08) at x264.c:1839
> #9  main (argc=<optimized out>, argv=<optimized out>) at x264.c:295
>
> Marat
>
> On Sun, Mar 3, 2013 at 12:57 AM, Jason Garrett-Glaser <jason at x264.com>wrote:
>
>> On Sat, Mar 2, 2013 at 9:42 PM, Marat Dukhan <maratek at gmail.com> wrote:
>> > It doesn't crash if I configure with --disable-asm.
>> > Still crashes if I configure with --extra-cflags="-O0 -mfpu=vfpv3".
>>
>> Can you post a backtrace?
>>
>> Jason
>> _______________________________________________
>> x264-devel mailing list
>> x264-devel at videolan.org
>> http://mailman.videolan.org/listinfo/x264-devel
>>
>
>
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20130303/127af1cf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Quick-fix-for-crash-in-foreman_cif.y4m-on-veryslow-p.patch
Type: application/octet-stream
Size: 1022 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20130303/127af1cf/attachment.obj>


More information about the x264-devel mailing list