3 ms·
It's not predictably happening with _all_ websocket server implementations. I tried with node.js using a combination of https and ws modules. That worked. We cr
by mntmn 14y ago
It's not predictably happening with _all_ websocket server implementations. I tried with node.js using a combination of https and ws modules. That worked. We crashed Chrome using em-websockt and netty, though.
- 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.