Bugzilla

bug 1734525 was what I was thinking of. I expect, given failures dried up there, that the stacks changed and then we ended up with new bugs. As noted there, Nika and I already did a bunch of triage/digging in that bug. We didn't understand then (and I still don't understand now) how it's possible for these requests to end up as "file not found". If there is some way of getting more information about the load by dumping more info in the crashing code, that may be  how we'd need to debug this. But I don't know how to do that, or what information would help elucidate where the NS_ERROR_FILE_NOT_FOUND would be coming from. Valentin?

(we could simply squash these errors by adding exceptions for these URLs (like [these existing ones](https://searchfox.org/mozilla-central/rev/9e3413f54ed6c9165b5659558091d766d34a731f/netwerk/base/nsNetUtil.cpp#3901-3913)) but I think the raciness here and the not understanding why/how it happens, means that that feels wrong - and given the symptoms are not entirely dissimilar to e.g. bug 1639821, I'd prefer understanding this more before resorting to just ignoring the error for these files.

bug 1734525 was what I was thinking of. I expect, given failures dried up there, that the stacks changed and then we ended up with new bugs. As noted there, Nika and I already did a bunch of triage/digging in that bug. We didn't understand then (and I still don't understand now) how it's possible for these requests to end up as "file not found". If there is some way of getting more information about the load by dumping more info in the crashing code, that may be  how we'd need to debug this. But I don't know how to do that, or what information would help elucidate where the NS_ERROR_FILE_NOT_FOUND would be coming from. Valentin?

We could simply squash these errors by adding exceptions for these URLs (like [these existing ones](https://searchfox.org/mozilla-central/rev/9e3413f54ed6c9165b5659558091d766d34a731f/netwerk/base/nsNetUtil.cpp#3901-3913)) but I think the raciness here and the not understanding why/how it happens, means that that feels wrong - and given the symptoms are not entirely dissimilar to e.g. bug 1639821, I'd prefer understanding this more before resorting to just ignoring the error for these files.