diff options
| author | Ronald S. Bultje <rsbultje@gmail.com> | 2017-04-06 11:47:03 -0400 |
|---|---|---|
| committer | Ronald S. Bultje <rsbultje@gmail.com> | 2017-04-07 13:29:45 -0400 |
| commit | 7f05c5cea04112471d8147487aa3b44141922d09 (patch) | |
| tree | 7869fd8f183c67e4794b87364103dc8231ad47c2 /tests/ref/fate/mpeg4-resolution-change-down-down | |
| parent | 8d94d9798a6903fc65ceb8e5af843cb6a793e045 (diff) | |
| download | ffmpeg-7f05c5cea04112471d8147487aa3b44141922d09.tar.gz | |
h264: don't re-call ff_h264_direct_ref_list_init() w/ frame-mt.
I'm hoping that this will address the remaining tsan fate-h264 issues:
WARNING: ThreadSanitizer: data race (pid=24478)
Read of size 8 at 0x7dbc0001c828 by main thread (mutexes: write M3243):
#0 ff_h264_ref_picture src/libavcodec/h264_picture.c:107 (ffmpeg+0x0000013b78d8)
[..]
Previous write of size 1 at 0x7dbc0001c82e by thread T2 (mutexes: write M3245):
#0 ff_h264_direct_ref_list_init src/libavcodec/h264_direct.c:137 (ffmpeg+0x000001382c93)
But I'm not sure because I haven't been able to reproduce locally.
Diffstat (limited to 'tests/ref/fate/mpeg4-resolution-change-down-down')
0 files changed, 0 insertions, 0 deletions