From eaec1182402d6aeac42fb2b36a758005f094e769 Mon Sep 17 00:00:00 2001 From: eladalon Date: Fri, 28 Jul 2017 02:25:09 -0700 Subject: [PATCH] Remove DCHECK from Call's ctor that could never fail I don't think this line could never conceivably fail - if the ctor has reached that point, the object fit in memory, and its members have all been allocated legal memory addresses, none of which may be 0x00. BUG=None Review-Url: https://codereview.webrtc.org/2989813002 Cr-Commit-Position: refs/heads/master@{#19176} --- webrtc/call/call.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/webrtc/call/call.cc b/webrtc/call/call.cc index 26d97aad52..25dcf32a62 100644 --- a/webrtc/call/call.cc +++ b/webrtc/call/call.cc @@ -417,7 +417,6 @@ Call::Call(const Call::Config& config, start_ms_(clock_->TimeInMilliseconds()), worker_queue_("call_worker_queue"), base_bitrate_config_(config.bitrate_config) { - RTC_DCHECK(&configuration_thread_checker_); RTC_DCHECK(config.event_log != nullptr); RTC_DCHECK_GE(config.bitrate_config.min_bitrate_bps, 0); RTC_DCHECK_GE(config.bitrate_config.start_bitrate_bps,