Use recursive mutex in CommandableFragmentGenerator to improve code clarity
Kurt noticed that the dataBufferDepthFragments_ parameter is not updated at the same time as the dataBufferDepthBytes_ parameter, mostly because it is bound to dataBuffer_.size(). To improve code clarity, it would probably be best to replace dataBufferDepthFragments_ with a function that locks the dataBufferMutex_ recursively and returns dataBuffer_.size().
#1 Updated by Eric Flumerfelt 7 months ago
I've implemented a change to feature/22068_CFG_UpdateDataBufferDepthFragmentsWithSize, where the DataBufferDepthFragments variable is updated at the same place as DataBufferDepthBytes. The original suggestion of using recursive_mutex was not easy to implement because the mutex in question was also being used to control condition_variables.