diff options
author | Akemi <der.richter@gmx.de> | 2017-02-23 01:37:23 +0100 |
---|---|---|
committer | Akemi <der.richter@gmx.de> | 2017-02-27 23:57:44 +0100 |
commit | 9bd819a0bc809ab5af300e5d73e88f120c5d0285 (patch) | |
tree | 136b475a23ba3c22eec79dd8bccd74327f2869a7 /video/decode/hw_cuda.c | |
parent | 55fb4cb3f6938e8494b8b9a5eec9d56e656cf46b (diff) | |
download | mpv-9bd819a0bc809ab5af300e5d73e88f120c5d0285.tar.bz2 mpv-9bd819a0bc809ab5af300e5d73e88f120c5d0285.tar.xz |
cocoa: fix segfault in certain circumstances
i falsely assumed that the windowDidChangeScreen was meant to report
‘physical’ screen changes but was wondering why it triggers on other
events too. it actually is a event that informs us when anything
referenced by our current NSScreen is changed. even when something
referenced in the NSScreen changed the old and new NSScreen are still
equal if the physical screen didn’t change. with that my previous
optimisation broke some cases where the physical screen didn’t change
but things it referenced did, leading to a segfault when theses were
accessed. to keep the optimisation we will always update our internal
NSScreen reference but the rest only when the physical screen was
changed.
Diffstat (limited to 'video/decode/hw_cuda.c')
0 files changed, 0 insertions, 0 deletions