diff options
| author | dequis <dx@dxzone.com.ar> | 2016-05-23 20:21:18 -0300 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2016-05-24 10:25:39 +0200 |
| commit | d941a57bd3c8d7a738c814a7da90ce7d04deac68 (patch) | |
| tree | ad5f202ca61789171a9c56307e02d1bd99b3c632 /osdep/win32/pthread.c | |
| parent | 6bd021e4ee30275ba6fe7d2e306909b57fd368dd (diff) | |
| download | mpv-d941a57bd3c8d7a738c814a7da90ce7d04deac68.tar.bz2 mpv-d941a57bd3c8d7a738c814a7da90ce7d04deac68.tar.xz | |
vo_xv: Handle incorrect size returned by Xv(Shm)CreateImage
Fixes #320 (which is closed as 'not our problem' but eh)
Relevant xorg bug: https://bugs.freedesktop.org/show_bug.cgi?id=70931
For me this happened when (accidentally) trying to play a 8460x2812 jpg
file with mpv. Like the referenced bug, xvinfo reports "maximum XvImage
size: 8192 x 8192". So the returned XvImage is 8192x2812 and memory
corruption happens.
Only after handling this BadShmSeg X11 errors are shown.
Diffstat (limited to 'osdep/win32/pthread.c')
0 files changed, 0 insertions, 0 deletions