UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36

Steps to reproduce the problem:
1. open 2 tabs in http://13.81.0.79:8085/
2. open dev tools - there'll be a number in the console, that's the id
3. In 1 of the tabs fill in 1st input box the other tab's id and connect
4. In the same tab, fill in the 2nd input box with 1200 and press create data
5. then click send data continuously

This will keep on sending 1200 packets synchronously until the bufferedAmount reaches an upper threshold, will stop until it reaches a lower threshold and send again...

What is the expected behavior?
I'd expect the send until bufer is full -> stop until buffer empty, cycles  to be very fast. And cpu to be mostly idle.

What went wrong?
But sometimes my computer never gets to the high buffer threshold because sending on a datachannel buffer of 1200 bytes is so cpu intensive.
If I'd change the buffer to 16000 and repeat this experiment, the cpu is a lot more idle, and actually the throughput measured on the other tab (the receiver) is much better

That's not the case on Firefox.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 57.0.2987.110  Channel: stable
OS Version: OS X 10.11.3
Flash Version: 

On Chrome 56, sometimes the connection would have sort of dropped entirely, meaning that after a few times dc.send would just do nothing, and no messages would be received on the other tab (even though the channel is still open on both ends)