Refactor RtpSender and SSRCDatabase a bit.

webrtc/modules/rtp_rtcp/source/ssrc_database.cc

Index: webrtc/modules/rtp_rtcp/source/ssrc_database.cc
diff --git a/webrtc/modules/rtp_rtcp/source/ssrc_database.cc b/webrtc/modules/rtp_rtcp/source/ssrc_database.cc
index fb02b7ef12cd12f785fd18ed331e1407d3fd38c4..87c0a897fd49303843b87dba477f903007325e39 100644
--- a/webrtc/modules/rtp_rtcp/source/ssrc_database.cc
+++ b/webrtc/modules/rtp_rtcp/source/ssrc_database.cc
@@ -11,26 +11,26 @@
 #include "webrtc/modules/rtp_rtcp/source/ssrc_database.h"
 
 #include "webrtc/base/checks.h"
-#include "webrtc/system_wrappers/include/clock.h"
-#include "webrtc/system_wrappers/include/critical_section_wrapper.h"
+#include "webrtc/system_wrappers/include/tick_util.h"
 
 namespace webrtc {
-namespace {
-uint64_t Seed() {
-  return Clock::GetRealTimeClock()->TimeInMicroseconds();
-}
-}  // namespace
 
-SSRCDatabase* SSRCDatabase::GetSSRCDatabase() {
-  return GetStaticInstance<SSRCDatabase>(kAddRef);
-}
+// For initializing the random seed, we don't use TimeInMicroseconds() since it
+// can return 0 on Mac if we're  called early on during process startup (e.g.
+// in tests).  This is because when the tick count gets converted into
+// microseconds, we can end up multiplying with 0 and end up with a seed of 0.
+SSRCDatabase::SSRCDatabase() : random_(TickTime::Now().Ticks()) {}

[stefan-webrtc, 2016/01/23 17:38:40]

Would it make sense to have a static metod in Random to get a seed and move this
comment there? Feels like we may end up having this comment in a lot of
different places otherwise.

[tommi, 2016/01/24 11:51:50]

Indeed - looks like all users of Random are calling the ctor with
clock_->TimeInMicroseconds().
It would be better to make the Random class take care of this but since it's in
webrtc/base, it can't depend on TickUtil, which is in system_wrappers.
I'll do it in a follow up CL.

 
-void SSRCDatabase::ReturnSSRCDatabase() {
-  GetStaticInstance<SSRCDatabase>(kRelease);
+SSRCDatabase::~SSRCDatabase() {
+  RTC_DCHECK(thread_checker_.CalledOnValidThread());
 }
 
+// TODO(tommi, holmer): Look into whether we can eliminate locking in this
+// class.  At the moment voe_auto_test requires it, but it's not clear if that's
+// an issue with the test code or if it reflects real world usage or if that's
+// the best design performance wise.
 uint32_t SSRCDatabase::CreateSSRC() {
-  CriticalSectionScoped lock(crit_.get());
+  rtc::CritScope lock(&crit_);
 
   while (true) {  // Try until get a new ssrc.
     // 0 and 0xffffffff are invalid values for SSRC.
@@ -42,19 +42,13 @@ uint32_t SSRCDatabase::CreateSSRC() {
 }
 
 void SSRCDatabase::RegisterSSRC(uint32_t ssrc) {
-  CriticalSectionScoped lock(crit_.get());
+  rtc::CritScope lock(&crit_);
   ssrcs_.insert(ssrc);
 }
 
 void SSRCDatabase::ReturnSSRC(uint32_t ssrc) {
-  CriticalSectionScoped lock(crit_.get());
+  rtc::CritScope lock(&crit_);
   ssrcs_.erase(ssrc);
 }
 
-SSRCDatabase::SSRCDatabase()
-    : crit_(CriticalSectionWrapper::CreateCriticalSection()), random_(Seed()) {}
-
-SSRCDatabase::~SSRCDatabase() {
-}
-
 }  // namespace webrtc