UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10991.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3524.2 Safari/537.36
Platform: 10991.0.0 (Official Build) dev-channel eve

Steps to reproduce the problem:
1. Call chrome.sockets.tcp.connect to a host that drops incoming TCP connections
2. close the socket
3. Future calls to chrome.sockets.tcpServer.listen do not call their callback

You can use the attached app:
1. Load the attached Chrome app (with chrome.sockets) permission
2. Open console, verify testtcpserver(), testudpserver() print out listening/bound socket info
3. Call break_chrome_socket_servers()
4. Verify testtcpserver() and testudpserver() no longer get listen/bind socket info.
5. You can check other apps such as https://chrome.google.com/webstore/detail/web-server-for-chrome/ofhbbkphhbklhfoeikjpcbhemlocgigb are also affected and no longer function for the login session
5. A full device reboot will make the problem go away, until  break_chrome_socket_servers() is called again.

What is the expected behavior?
Calls to tcpServer.listen and udp.bind should call their callback.

What went wrong?
tcpServer.listen and udp.bind never call their callback.

Did this work before? Yes 67.0.3396.99 (Official Build) (64-bit)

Does this work in other browsers? Yes

Chrome version: 70.0.3524.2  Channel: dev
OS Version: 10991.0.0
Flash Version: 30.0.0.142 

This bug does not reproduce on the current ChromeOS stable channel (67).
This bug does not appear when tested on OSX Chrome Canary
This bug does not appear with tested on OSX Chrome Stable
 

Deleted: background.js 1.6 KB

background.js 1.6 KB View Download

Deleted: manifest.json 511 bytes

manifest.json 511 bytes View Download