Move the call to enable the WebRTC event log from PeerConnectionFactory to PeerConnection.

content/browser/renderer_host/media/peer_connection_tracker_host.h

Index: content/browser/renderer_host/media/peer_connection_tracker_host.h
diff --git a/content/browser/renderer_host/media/peer_connection_tracker_host.h b/content/browser/renderer_host/media/peer_connection_tracker_host.h
index 53a96302e04bf3b7c52d2de792ada290a6d82267..53926f87c8191f2d1b879ac62c5a3b6b1f9ba45f 100644
--- a/content/browser/renderer_host/media/peer_connection_tracker_host.h
+++ b/content/browser/renderer_host/media/peer_connection_tracker_host.h
@@ -19,6 +19,8 @@ class ListValue;
 
 namespace content {
 
+class WebRTCEventLogHost;
+
 // This class is the host for PeerConnectionTracker in the browser process
 // managed by RenderProcessHostImpl. It receives PeerConnection events from
 // PeerConnectionTracker as IPC messages that it forwards to WebRTCInternals.
@@ -26,7 +28,8 @@ namespace content {
 class PeerConnectionTrackerHost : public BrowserMessageFilter,
                                   public base::PowerObserver {
  public:
-  explicit PeerConnectionTrackerHost(int render_process_id);
+  PeerConnectionTrackerHost(int render_process_id,
+                            WebRTCEventLogHost* event_log_host);
 
   // content::BrowserMessageFilter override.
   bool OnMessageReceived(const IPC::Message& message) override;
@@ -57,6 +60,8 @@ class PeerConnectionTrackerHost : public BrowserMessageFilter,
 
   int render_process_id_;
 
+  WebRTCEventLogHost* const event_log_host_;

[Henrik Grunell, 2016/06/01 08:31:11]

Is the event log host guaranteed to outlive the PC tracker?

[Ivo-OOO until feb 6, 2016/06/02 14:43:39]

Both are members of RenderProcessHostImpl, so they should have the same
lifetime.

[Henrik Grunell, 2016/06/03 07:40:52]

OK, then one will be deleted before the other, so it depends on that order.
Please check this, and if you decide to depend on the order comment on that
clearly in the RPHI class declaration, i.e. at the member variables.

[Ivo-OOO until feb 6, 2016/06/03 16:07:01]

Actually, I don't think that the order matters in this case. Since
WebRTCEventLogHost is only ever accessed from the Browser::UI thread, I don't
think it's possible that any calls to WebRTCEventLogHost happen during the
tearing down of the RenderProcessHost, which also happens on the Browser::UI
thread.

+
   DISALLOW_COPY_AND_ASSIGN(PeerConnectionTrackerHost);
 };