Issue metadata
Sign in to add a comment
|
Add option to disable websocket network inspector
Reported by
jf.pamb...@gmail.com,
Apr 18 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Steps to reproduce the problem: As Issue 594950 noted, Chrome hangs completely with devtools open in a tabs with heavy websocket usage. Our web application downloads several 100s mb of data via websocket in a worker. With devtools closed, the experience is perfect, frame time is 16ms. With devtools open, even while not looking at the network tabs. The browser and all opened tabs/instances hangs completely (no refresh of the UI at all) during the entire transfer which also takes much longer than usual. I understand from #594950 that moving the websocket data across process for the purpose of the network inspector is the issue, but I wonder if that could be disable. What is the expected behavior? Being able to use devtools. What went wrong? All windows/tabs of Chrome hangs for 30-60s or until the websocket data transfer stops. Did this work before? N/A Chrome version: 66.0.3359.117 Channel: stable OS Version: Flash Version:
,
Apr 19 2018
,
Apr 19 2018
jf.pambrun@ Thanks for the issue. CC'ing allada@ - owner of the issue 594950 for further inputs on this issue. Thanks...
,
Apr 23 2018
,
May 9 2018
,
May 14 2018
,
Jun 26 2018
,
Oct 12
,
Nov 9
Fixing #594950 should fix your issue as well without needing to explicitly disable |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by davidben@chromium.org
, Apr 18 2018