It looks like it’s an issue reported with chromes old version and was fixed in a update for chrome.
Try set another client on the webview and see if that works.
It seems to be a issue with the way chrome gets the buffer from the socket and tries to decode it.