https://bugs.kde.org/show_bug.cgi?id=375839
--- Comment #10 from Ronald S. Bultje <rsbul...@gmail.com> ---
We're still seeing the issue in FFmpeg. This is valgrind r16297 with vex r3344.
==15422== Memcheck, a memory error detector
==15422== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==15422== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright
info
==15422== Command:
/home/fate/workdirs/x86_64-archlinux-gcc-valgrindundef/build/ffmpeg -nostdin
-nostats -cpuflags all -hwaccel none -threads 1 -thread_type frame+slice -i
/home/fate/fate-suite/vp9-test-vectors/vp90-2-00-quantizer-01.webm -flags
+bitexact -fflags +bitexact -f framemd5 -
==15422==
ffmpeg version N-85439-g03eb0515c1 Copyright (c) 2000-2017 the FFmpeg
developers
built with gcc 6.3.1 (GCC) 20170306
configuration:
--prefix=/home/fate/workdirs/x86_64-archlinux-gcc-valgrindundef/install
--samples=/home/fate/fate-suite --enable-gpl --enable-memory-poisoning
--enable-avresample --cc='ccache cc'
--target-exec='/home/fate/src/valgrind/vg-in-place --error-exitcode=1
--malloc-fill=0xa2 --track-origins=yes --leak-check=full --gen-suppressions=all
--suppressions=/home/fate/ffmpeg/tests/fate-valgrind.supp' --disable-stripping
--disable-memory-poisoning
libavutil 55. 60.100 / 55. 60.100
libavcodec 57. 92.100 / 57. 92.100
libavformat 57. 72.100 / 57. 72.100
libavdevice 57. 7.100 / 57. 7.100
libavfilter 6. 84.101 / 6. 84.101
libavresample 3. 6. 0 / 3. 6. 0
libswscale 4. 7.100 / 4. 7.100
libswresample 2. 8.100 / 2. 8.100
libpostproc 54. 6.100 / 54. 6.100
VEX temporary storage exhausted.
Pool = TEMP, start 0x38fbed68 curr 0x39477e28 end 0x394838a7 (size 5000000)
vex: the `impossible' happened:
VEX temporary storage exhausted.
Increase N_{TEMPORARY,PERMANENT}_BYTES and recompile.
vex storage: T total 946892552 bytes allocated
vex storage: P total 640 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==15422== at 0x38085C13: show_sched_status_wrk (m_libcassert.c:378)
==15422== by 0x38085D14: report_and_quit (m_libcassert.c:449)
==15422== by 0x38085F51: panic (m_libcassert.c:525)
==15422== by 0x38085F51: vgPlain_core_panic_at (m_libcassert.c:530)
==15422== by 0x38085F7A: vgPlain_core_panic (m_libcassert.c:535)
==15422== by 0x380A1EE2: failure_exit (m_translate.c:740)
==15422== by 0x38153748: vpanic (main_util.c:231)
==15422== by 0x381537B4: private_LibVEX_alloc_OOM (main_util.c:171)
==15422== by 0x38179650: LibVEX_Alloc_inline (main_util.h:167)
==15422== by 0x38179650: doRegisterAllocation
(host_generic_reg_alloc2.c:517)
==15422== by 0x3815167C: libvex_BackEnd (main_main.c:1122)
==15422== by 0x3815167C: LibVEX_Translate (main_main.c:1225)
==15422== by 0x380A4725: vgPlain_translate (m_translate.c:1770)
==15422== by 0x380DAD7B: handle_chain_me (scheduler.c:1080)
==15422== by 0x380DC73F: vgPlain_scheduler (scheduler.c:1424)
==15422== by 0x380EBB56: thread_wrapper (syswrap-linux.c:103)
==15422== by 0x380EBB56: run_a_thread_NORETURN (syswrap-linux.c:156)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 15422)
==15422== at 0xCC33BF: ff_vp9_iadst_iadst_16x16_add_avx2 (vp9itxfm.asm:2151)
==15422== by 0xB7D794: ff_vp9_decode_block (vp9block.c:1387)
==15422== by 0x1: ???
==15422== by 0x70CB63F: ???
==15422== by 0xB: ???
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
