This bug is publicly visible.
At the moment, we have relatively frequent log pollution due to network events which are missing the responseStarted event. This usually shows up in the logs as
JavaScript error: chrome://remote/content/shared/listeners/NetworkEventRecord.sys.mjs, line 328: TypeError: can't access property "setResponseSizes", this[#response] is null
We should investigate individual cases which lead to missing events, but at the moment we don't even log the URL of the skipped event, so it makes it difficult to investigate.
I suggest to add a guard at https://searchfox.org/mozilla-central/rev/55837bbe3e47f9b4fa91ef83a44b53823626f01d/remote/shared/listeners/NetworkEventRecord.sys.mjs#328
this.#response.setResponseSizes(sizes);
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3