UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.41 Safari/537.36

Steps to reproduce the problem:
1. Start adb server. Make sure it listens on port 5037.
2. Create a Chrome app with tcp-connect permission
3. Open its background page
4. Run this script:

var c = 0, t = Date.now();
function test() {
  chrome.socket.create('tcp', {}, ({socketId}) => {
    if (socketId == 0) throw Error('failed to create socket');
    chrome.socket.connect(socketId, '127.0.0.1', 5037, connectInfo => {
      if (connectInfo < 0) throw Error('failed to connect');
      var data = new ArrayBuffer(4);
      new Uint8Array(data).set(Uint8Array.of(48, 48, 48, 48));
      chrome.socket.write(socketId, data, writeInfo => {
        if (writeInfo.bytesWritten == 0) throw Error('failed to write');
        console.log(++c, Date.now() - t);
        if (c < 10000) setTimeout(test, 0);
      });
    });
  });
}
test();

What is the expected behavior?

What went wrong?
After ~7800 iterations the connection fails. After that moving the mouse over the background page causes rendering artifacts, and after a while Chrome crashes.

Crashed report ID: crash/a28315bc00000000

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 52.0.2743.41  Channel: stable
OS Version: Ubuntu 14.04 LTS
Flash Version: Shockwave Flash 22.0 r0