Glenn Kasten 91540aeb6c Fix theoretical race condition in addOutputTrack
This is not a real race, because addOutputTrack was only called in two
places, and in both places there could be no other threads referencing
the DuplicatingThread instance.

Those two places are:
 - the DuplicatingThread constructor, which is of course safe
 - openDuplicateOutput - this is safe because it's called immediately
   after the new DuplicatingThread, and there are no sp<> either in the
   constructor or here which could cause onFirstRef() to do Thread::run().

But for safety in case addOutputTrack is ever called somewhere else,
or there are sp<> created earlier, it is safer to take the thread lock.

Change-Id: I1502d014fa37ec5dbf4bf40d3e2884af311cd5e9
2012-02-24 14:20:29 -08:00
2012-02-16 16:42:20 -08:00
2012-02-16 19:26:35 -08:00
2012-02-15 11:30:51 -08:00
2012-02-20 22:38:43 -08:00
2012-02-20 22:38:43 -08:00
2012-02-16 15:03:42 -08:00
2012-01-17 11:57:27 -08:00
2012-02-10 11:41:41 -08:00
Description
No description provided
5.1 GiB
Languages
Java 77.3%
Kotlin 9.2%
PowerBuilder 6.6%
C++ 5.5%
AIDL 1%