Remove statistics tracking from FrameBuffer2
This was only set to nullptr in non-test environments and was thusly unused. With this change, the stats callbacks are gaurenteed to only come from the VideoStreamBufferController and so the thread checks can be removed. Bug: webrtc:14003 Change-Id: Iaf0e77aa7c45a317e38ae27739edcefd3123d832 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/272021 Reviewed-by: Erik Språng <sprang@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Commit-Queue: Evan Shrubsole <eshr@webrtc.org> Cr-Commit-Position: refs/heads/main@{#37816}
This commit is contained in:
committed by
WebRTC LUCI CQ
parent
c48f9ef354
commit
de7ae5755b
@ -48,7 +48,6 @@ class FrameBuffer {
|
||||
public:
|
||||
FrameBuffer(Clock* clock,
|
||||
VCMTiming* timing,
|
||||
VCMReceiveStatisticsCallback* stats_callback,
|
||||
const FieldTrialsView& field_trials);
|
||||
|
||||
FrameBuffer() = delete;
|
||||
@ -143,10 +142,6 @@ class FrameBuffer {
|
||||
FrameMap::iterator info)
|
||||
RTC_EXCLUSIVE_LOCKS_REQUIRED(mutex_);
|
||||
|
||||
void UpdateJitterDelay() RTC_EXCLUSIVE_LOCKS_REQUIRED(mutex_);
|
||||
|
||||
void UpdateTimingFrameInfo() RTC_EXCLUSIVE_LOCKS_REQUIRED(mutex_);
|
||||
|
||||
void ClearFramesAndHistory() RTC_EXCLUSIVE_LOCKS_REQUIRED(mutex_);
|
||||
|
||||
// The cleaner solution would be to have the NextFrame function return a
|
||||
@ -179,7 +174,6 @@ class FrameBuffer {
|
||||
std::vector<FrameMap::iterator> frames_to_decode_ RTC_GUARDED_BY(mutex_);
|
||||
bool stopped_ RTC_GUARDED_BY(mutex_);
|
||||
VCMVideoProtection protection_mode_ RTC_GUARDED_BY(mutex_);
|
||||
VCMReceiveStatisticsCallback* const stats_callback_;
|
||||
int64_t last_log_non_decoded_ms_ RTC_GUARDED_BY(mutex_);
|
||||
|
||||
// rtt_mult experiment settings.
|
||||
|
||||
Reference in New Issue
Block a user