diff options
| author | wm4 <wm4@nowhere> | 2017-01-22 15:23:35 +0100 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2017-01-22 15:24:13 +0100 |
| commit | 5c942128d80b358e53239d56d90cb1b3189a1243 (patch) | |
| tree | 66e428b8dcebe5587fc6f15e37f0315d008b5c66 /sub | |
| parent | 06c55ac6c32a21419cfc55bbb773e922816991fe (diff) | |
| download | mpv-5c942128d80b358e53239d56d90cb1b3189a1243.tar.bz2 mpv-5c942128d80b358e53239d56d90cb1b3189a1243.tar.xz | |
player: actually initialize/destroy MPContext.lock
Seems like quite on oversight.
For most of the better pthread implementations, pthread_mutex_init() on
an already 0-initialized memory block is probably a no-op, but of course
we should do things correctly. Also could setup analysis tools.
Diffstat (limited to 'sub')
0 files changed, 0 insertions, 0 deletions