User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

Just use browser.
Appears sometimes.

Actual results:

See errors:

JavaScript error: https://cdn.digitru.st/prod/1.5.33/dt.html, line 114: SyntaxError: An invalid or illegal string was specified
JavaScript error: resource:///actors/PageStyleChild.jsm, line 35: SecurityError: Permission denied to access property "document" on cross-origin object
JavaScript error: https://cdn.digitru.st/prod/1/digitrust.min.js, line 1: Error: [DigiTrust Iframe Error] Client could not connect to the iframe
JavaScript error: moz-extension://0e34cc0f-daaf-4976-a261-e73661f81f77/background.js, line 525: Error: Could not establish connection. Receiving end does not exist.
JavaScript error: https://www.howtogeek.com/195430/how-to-create-a-strong-password-and-remember-it/, line 1626: TypeError: e.querySelector(...) is null
JavaScript error: resource://gre/modules/WebRequestContent.js, line 143: SecurityError: Permission denied to access property "windowUtils" on cross-origin object
JavaScript error: resource://gre/modules/WebRequestContent.js, line 143: SecurityError: Permission denied to access property "windowUtils" on cross-origin object
JavaScript error: resource://gre/modules/WebRequestContent.js, line 143: SecurityError: Permission denied to access property "windowUtils" on cross-origin object
JavaScript error: resource://gre/modules/WebRequestContent.js, line 143: SecurityError: Permission denied to access property "windowUtils" on cross-origin object
JavaScript error: resource://gre/modules/WebRequestContent.js, line 143: SecurityError: Permission denied to access property "windowUtils" on cross-origin object
JavaScript error: resource:///modules/sessionstore/SessionStore.jsm, line 2734: TypeError: aChannel.switchProcessTo is not a function

Expected results:

No errors...

Hi Wellington,

Could you please be more specific on how to reproduce this bug? Like, were you on facebook, reading news, playing games, watching a movie, reading an article? The error you got it from the web console, right? Did you see any error on the web?

On the other hand, maybe you can provide me with a bit more info. Does this issue occur with a fresh profile? you can find the steps here: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Can you please download Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem and see if the issue still occurs there as well?

If after doing this you can still reproduce the bug, could you send me a screenshot or a video of the bug? That always helps a lot.

Thanks in advance, Flor.

Hi,

maybe related to fission feature. "fission.autostart".

Thanks!

Hi,

I've tried to reproduce this bug on UBUNTU 18.04 64 bits with the latest version of nightly but wasn't able to reproduce it. Could you please share an URL where you've seen this error? Maybe a screenshot?

On the other hand, as I asked before, were you able to reproduce this bug with a clean profile or the latest version of nightly?

Thanks in advance, Flor.

Hi Wellington,

I'm marking this as Resolved-Incomplete due to lack of response. If the issue is still reproducible with the latest Firefox version, feel free to reopen the bug with more information.

Best regards, Flor.

I assume this comes from:
https://searchfox.org/mozilla-central/rev/3a61fb322f74a0396878468e50e4f4e97e369825/toolkit/components/extensions/webrequest/WebRequestContent.js#181

And yes this is Fission related. Based on the source of failure, moving it to the correct component for further investigation.

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Since WebRequestContent.js is removed in bug 1631933, this should no longer be an issue.