From 5c942128d80b358e53239d56d90cb1b3189a1243 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sun, 22 Jan 2017 15:23:35 +0100 Subject: 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. --- player/main.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'player') diff --git a/player/main.c b/player/main.c index 8f54b98728..87ec1ab70b 100644 --- a/player/main.c +++ b/player/main.c @@ -199,6 +199,7 @@ void mp_destroy(struct MPContext *mpctx) pthread_detach(pthread_self()); mp_msg_uninit(mpctx->global); + pthread_mutex_destroy(&mpctx->lock); talloc_free(mpctx); } @@ -335,6 +336,8 @@ struct MPContext *mp_create(void) .playback_abort = mp_cancel_new(mpctx), }; + pthread_mutex_init(&mpctx->lock, NULL); + mpctx->global = talloc_zero(mpctx, struct mpv_global); // Nothing must call mp_msg*() and related before this -- cgit v1.2.3