diff options
author | Aaron Levinson <alevinsn@aracnet.com> | 2017-05-16 05:04:36 -0700 |
---|---|---|
committer | Mark Thompson <sw@jkqxz.net> | 2017-05-16 22:04:49 +0100 |
commit | f125c54b7a5f7b3d742aab2b11a59b7a4eaf4d74 (patch) | |
tree | 0ef2e56e7f9570cd23349cd16a0fd6944ac5cb18 /libavcodec/jpeg2000dsp.c | |
parent | 75f9fe1519deba4285cbc8cb5b8919b97ba40366 (diff) | |
download | ffmpeg-f125c54b7a5f7b3d742aab2b11a59b7a4eaf4d74.tar.gz |
avutil/hwcontext_dxva2: Don't improperly free IDirect3DSurface9 objects
Add dxva2_pool_release_dummy() and use it in call to
av_buffer_create() in dxva2_pool_alloc().
Prior to this change, av_buffer_create() was called with NULL for the
third argument, which indicates that av_buffer_default_free() should
be used to free the buffer's data. Eventually, it gets to
buffer_pool_free() and calls buf->free() on a surface object (which is
av_buffer_default_free()).
This can result in a crash when the debug version of the C-runtime is
used on Windows. While it doesn't appear to result in a crash when
the release version of the C-runtime is used on Windows, it likely
results in memory corruption, since av_free() is being called on
memory that was allocated using
IDirectXVideoAccelerationService::CreateSurface().
Signed-off-by: Aaron Levinson <alevinsn@aracnet.com>
Reviewed-by: wm4 <nfxjfg@googlemail.com>
Reviewed-by: Steven Liu <lingjiujianke@gmail.com>
Reviewed-by: Mark Thompson <sw@jkqxz.net>
(cherry picked from commit 0c1c514643d5e1645160d697fa4c27cd38c7c791)
Diffstat (limited to 'libavcodec/jpeg2000dsp.c')
0 files changed, 0 insertions, 0 deletions