> I can understand using a few resources in the background to serve some of that data, but it must never get in the way of actual work getting done. Which is e

> I can understand using a few resources in the background to serve some of that data, but it must never get in the way of actual work getting done. Which is exactly how the code was intended to work. Firefox did not design their software to hang in the event of telementry losing internet access. I don't know firefox's internal architecture or its development, what follows is pure conjecture. Their intention seems to be to slowly migrate the codebase from C++ to Rust. That telemetry is the only function to so far rely on their new rust networking library viaduct (and thus trigger the bug) could be because they wanted use their least important fucntionality as a test bed. In which case, if there wasn't any telemetry, a different piece of code would have been migrated to rust first and triggered this same bug. Without the telemtry, it would have presumably taken them longer to realise that things had broken, let alone resolve it.