Bug 1930848 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
At the moment, we have relatively frequent log pollution due to network events for which we 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
```js
this.#response.setResponseSizes(sizes);
```
Revision 1 by
on 
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
```js
this.#response.setResponseSizes(sizes);
```

Back to Bug 1930848 Comment 0