4 ms·
(i'm on the chrome dev relations team, btw) We have a few people looking at the ticket now.. looks like its within our websocket implementation and not at the
by paulirish 14y ago
(i'm on the chrome dev relations team, btw)
We have a few people looking at the ticket now.. looks like its within our websocket implementation and not at the SSL layer. Still reducing though..
We could use some crash IDs if you have any. To get those: Assuming crash reporting is enabled, head to about:crashes and grab any crash ID associated with this event. And drop them in a comment on the ticket. Thank you much.