All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=754608

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=33e23dbcc607524ef44d9660405b1733a86602af0e678dc25c49bb71d4d08f64


Bot(s) for this bug's original alert(s):

webrtc-android-tests-nexus5-kitkat
webrtc-win-large-tests

Increased memory usage due to https://codereview.webrtc.org/2994093002.

philipel: Please close if the increase is within the expectations :)

It's a bit unfortunate that it has such a big memory impact on large meetings (10% mem increase for 15 person meetings).

It seems like it would be pretty safe to reduce from 512 to, say, 128 and still not hit the bug. WDYT?

sprang@, do you know how common frames larger than 100 packets are?

In practice the change in memory usage is not that big. A buffer of 512 packets has the size of ~720 kB, and in the context of running webrtc in chrome it doesn't matter much. Also, this is a temporary workaround, so it should be gone in M63.

Even if we wanted to reduce the start size there is a risk of frames being larger than 128 packets when doing screensharing.