4 ms·
... due to code in Telemetry being different and triggering different code paths in the network stack. There is a why here, and it includes Telemetry mixed tra
by barrkel 5y ago
... due to code in Telemetry being different and triggering different code paths in the network stack.
There is a why here, and it includes Telemetry mixed traffic as a potential culprit. There are reasons to unify traffic (proxy support, QoS and whatnot) but unification of the user and Telemetry streams isn't without risk, as has been shown.
- cxr 5y ago> unification of the user and Telemetry streams isn't without risk, as has been shown A constant refrain over the last 10 years or so of Mozilla's descent while trying to justify the removal of features from Firefox has been that not doing so unnecessarily bloats the surface area of the codebase, and specifically that this increases the chance of vulnerabilities and defects. Will the same argument be applied here, now with a case in hand, to justify the removal of telemetry, too?
- marcan_42 5y agoIt's the same app. I don't get why you're replying to every thread trying to somehow argue that sharing a thread for all network code is a bad thing and telemetry needs to be a special snowflake that gets a different thread. The networking code had an infinite loop bug. It was triggered by telemetry, but it could've been anything. Telemetry getting its own network thread wouldn't have magically made it impossible for it to cause problems. Bugs happen, and sometimes make things interact in weird ways.