Manfred Georg 7f4eb4f6c6 set ffmpeg mutex to NULL on destruction.
The Mutex manager registered with ffmpeg must reset the mutex to NULL after destruction, otherwise ffmpeg will give the invalid mutex to the next mutex manager when it asks it to CREATE a new mutex.
See ffmpeg code: http://git.videolan.org/?p=ffmpeg.git;a=blob;f=libavcodec/utils.c;h=28c5785398fcf11a3d3c70a8cd09e9df798e2734;hb=HEAD#l3423

Cherry picked from head (file has moved but issue is the same).
Conflicts:
	modules/videoio/src/cap_ffmpeg_impl.hpp
2014-09-26 10:19:34 -07:00
..
2014-07-11 09:22:55 +02:00
2014-08-28 14:47:26 +04:00
2014-09-17 09:30:19 +02:00
2014-06-26 16:29:45 +02:00
2014-05-12 15:26:56 +02:00
2014-03-02 21:04:17 +04:00
2014-07-02 11:54:20 +04:00
2014-04-08 16:10:32 +03:00
2014-06-24 11:52:56 +01:00