[x264-devel] libx264 crashing when it is used with libtcmalloc.so.4
Raghavender Palla
raghavender.palla at gmail.com
Mon Nov 13 06:26:54 CET 2017
Hi,
Anyone please tell whom to contact for these kind of issues ?
Thanks & Regards,
Raghavender.
On Fri, Nov 10, 2017 at 6:01 PM, Raghavender Palla <
raghavender.palla at gmail.com> wrote:
> Hi,
>
> Can some one help on this x264 lib crash issue please ?
>
> Thanks & Regards,
> Raghavender.
>
>
> On Wed, Nov 8, 2017 at 11:17 AM, Raghavender Palla <
> raghavender.palla at gmail.com> wrote:
>
>>
>> Hi,
>>
>> I am using libx264 lib to encode h264 video.
>>
>> Code base used is: x264-snapshot-20120303-2245-stable (
>> http://download.videolan.org/x264/snapshots/x264-snapshot-20
>> 120303-2245-stable.tar.bz2 )
>>
>> Compiled the code and used along with libtcmalloc.so.4 in our application.
>>
>> Linux: RHEL 7.1
>>
>> I am getting crash and seeing the following BT.
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> x264_macroblock_cache_load (b_mbaff=0, mb_y=48201728, mb_x=0,
>> h=0x1536008) at common/macroblock.c:1074
>> 1074 M128( h->mb.cache.mv[l][i8] ) = M128_ZERO;
>> Missing separate debuginfos, use: debuginfo-install
>> glibc-2.17-78.el7.x86_64 libgcc-4.8.3-9.el7.x86_64
>> libstdc++-4.8.3-9.el7.x86_64 xz-libs-5.1.2-9alpha.el7.x86_64
>> zlib-1.2.7-13.el7.x86_64
>> (gdb) bt
>> #0 x264_macroblock_cache_load (b_mbaff=0, mb_y=48201728, mb_x=0,
>> h=0x1536008) at common/macroblock.c:1074
>> #1 x264_macroblock_cache_load_progressive (h=h at entry=0x1536008,
>> mb_x=mb_x at entry=0, mb_y=mb_y at entry=0) at common/macroblock.c:1360
>> #2 0x00007ffff73ed6a1 in x264_slice_write (h=h at entry=0x1536008) at
>> encoder/encoder.c:2171
>> #3 0x00007ffff73ee1cc in x264_slices_write (h=h at entry=0x1536008) at
>> encoder/encoder.c:2474
>> #4 0x00007ffff73f2d9b in x264_encoder_encode (h=0x1536008,
>> pp_nal=0x7fffffffdca0, pi_nal=0x7fffffffdca8, pic_in=<optimized out>,
>> pic_out=0x7fffffffdbe0) at encoder/encoder.c:3059
>>
>>
>> It crashed at this line in common/macroblock.c file.
>> >>>>>> M128( h->mb.cache.mv[l][i8] ) = M128_ZERO; ------> this line is
>> crashing.
>>
>> Anyone faced this issue earlier ? And is it anything do with the options
>> used while building libX264 ?
>> Any relation with __m128 and tcmalloc compatibility issue as the issue is
>> coming when libtcmalloc is used.
>>
>> Can some one help on this ?
>>
>> Thanks & Regards,
>> Raghavender Palla
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20171113/957c20c7/attachment.html>
More information about the x264-devel
mailing list