)]}'
{
  "commit": "89aad9e16814ac610a2b6409a803c584076c49b0",
  "tree": "190f9d5db69bbf3983bc0aa0af42b96d769ca9b0",
  "parents": [
    "512bdce7141371a7db54b10d52f90505342efe1f"
  ],
  "author": {
    "name": "Elad Alon",
    "email": "eladalon@webrtc.org",
    "time": "Wed Apr 18 12:02:21 2018"
  },
  "committer": {
    "name": "Commit Bot",
    "email": "commit-bot@chromium.org",
    "time": "Wed Apr 25 10:33:43 2018"
  },
  "message": "Remove the limit on concurrent RtcEventLogImpl instances\n\nThe limit was introduced to avoid spawning too many threads.\nIt had the downside that the peer connections which have an\nassociated RtcEventLogImpl instance, are not necessarily those\nwhich we wish to log.\nAfter this CL, it becomes the responsibility of the application\nhosting WebRTC to limit the number of peer connections to a\nnumber which it can support, including thread resources.\n\nBug: webrtc:9046\nChange-Id: I7444a6020dd51583c666285655af986def53faa4\nReviewed-on: https://webrtc-review.googlesource.com/70661\nCommit-Queue: Elad Alon \u003celadalon@webrtc.org\u003e\nReviewed-by: Dino Radaković \u003cdinor@webrtc.org\u003e\nReviewed-by: Björn Terelius \u003cterelius@webrtc.org\u003e\nCr-Commit-Position: refs/heads/master@{#23019}",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "943d90b63e7ec02c78dc8d1f1a73418b7eecc2d1",
      "old_mode": 33188,
      "old_path": "logging/rtc_event_log/rtc_event_log_impl.cc",
      "new_id": "74f88779ef70a197bc3020f23dd864092a43bd83",
      "new_mode": 33188,
      "new_path": "logging/rtc_event_log/rtc_event_log_impl.cc"
    }
  ]
}