Web pages never load - Firefox Nightly, uBlock 1.18.4

[sciguyryan]

Prerequisites

• I verified that this is not a filter issue
  • Filter issues MUST be reported at filter issue tracker
• This is not a support issue or a question
  • Support issues and questions are handled at /r/uBlockOrigin
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue
  • Your issue may already be reported.
• I tried to reproduce the issue when...
  • uBlock Origin is the only extension
  • uBlock Origin with default lists/settings
  • using a new, unmodified browser profile
• I am running the latest version of uBlock Origin
• I checked the documentation to understand that the issue I report is not a normal behavior

Description

Pages will not load in Firefox nightly (after 28/1/2019) with uBlock enabled. Pages will never load as soon as the addon is enabled. Disabling the addon instantly corrects the issue. This appears to function everywhere.

I had initially thought that Mozilla had somehow broken things, though after going through and disabling addons one at a time it appears to be a uBlock related issue.

The following can be found in the browser console: https://pastebin.com/GXbeDXnm

A specific URL where the issue occurs

https://google.com/

Steps to Reproduce

1. Enabled uBlock.
2. Refresh a web page. Pages will not load at all.
3. Disable uBlock (or revert the browser to the 28/1 build).
4. Web pages will once again load.

Expected behavior:

Pages should load correctly with the addon enabled.

Actual behavior:

Pages never finish loading with the addon enabled.

Your environment

• uBlock Origin version: 1.18.4
• Browser Name and version: Firefox Nightly - 28/01/2019 build
• Operating System and version: WIndows 10, 64-bit.

[uBlock-user]

The following can be found in the browser console: https://pastebin.com/GXbeDXnm

Your nightly appears to be a broken build. I'm on 67.0a1 (2019-02-02) (64-bit) and cannot reproduce.

[uBlock-user]

Update to the latest nightly and try to reproduce.

[sciguyryan]

Update to the latest nightly and try to reproduce.

I did, hence step 3. I can resolve the issue by either downgrading nightly or by disabling uBlock.

[uBlock-user]

Firefox Nightly - 28/01/2019 build

but your browser version says January build, this is why i said update to the latest nightly build

I can resolve the issue by either downgrading nightly

So nightly is broken then, I'm updating to the latest Nightly. I will post if I can reproduce there.

[uBlock-user]

Updated to the latest Nightly on my device, web pages load normally as expected, but I do see one debug console error like you do.

[sciguyryan]

I'm going to give a clean profile a try and see if I can unpick what's going on then. It's particularly odd that it works perfectly if I revert back to the specific nightly build, though.

[uBlock-user]

Nightly is unstable and can be broken at any new build, so not a surprise.

[gorhill]

There is a wasm error in your console which make me think your indexedDB storage is corrupted. If you know were to find it, you could delete it manually and try restart uBO again.

[LinuxOnTheDesktop]

I have a somewhat similar problem; tell me whether I should open a new issue, please.

My problem is as follows and pertains to Firefox 65.0 (which is a 'release' build). When Firefox is open, and I click a link in Thunderbird, then, sometimes - depending on the URL? - and only when Ublock Origin is enabled for the page in question, the following occurs. Firefox will not load the page and indeed parts of the Firefox UI do not work. I have had this problem with URLs starting: https://bugzilla.mozilla.org/

EDIT: and I see this in the Firefox console:

Content Security Policy: Ignoring "'unsafe-inline'" within script-src or style-src: nonce-source or hash-source specified
Content Security Policy: The page's settings blocked the loading of a resource at inline ("script-src"). show_bug.cgi:1:1
Loading failed for the <script> with source “https://bugzilla.mozilla.org/static/v20190130.1/extensions/GoogleAnalytics/web/js/analytics.js”.

[weaversam8]

I have also experienced this issue. Logged into my laptop today to find no web pages loading. I'm running Firefox Developer Edition, 66.0b6 build ID 20190207161357, update channel aurora, on Windows 10.

Disabling the add-on fixed the problem, and the problem persisted even after the add-on was uninstalled, reinstalled, and reset to default settings.

[gorhill]

Any errors reported at the browser console? (ctrl-shift-J)

Also, try with a new fresh profile.

[weaversam8]

Tried both in a fresh profile and in my existing profile and the issue has entirely disappeared. Unable to reproduce all of a sudden :/

[LinuxOnTheDesktop]

@weaversam8

So in both your case and mine the problem suddenly disappeared. It does not seem as though there was some thing we both did, so I infer that the problem is intermittent, i.e. dependent on things we know not. But perhaps I miss something.

[gorhill]

There was an issue resembling this in bugzilla, https://bugzilla.mozilla.org/show_bug.cgi?id=1496684, but this was affecting Firefox for Android. I wonder if a similar, rare condition could also be occurring in Firefox Desktop.

Also, one thing I wonder is if the code here can be re-entrant -- I have assumed it is not. If there is re-entrance, this could cause some network requests to never be processed at start up. I strongly doubt re-entrance is possible, but nevertheless I will modify to be shielded against this in the next dev build.

[weaversam8]

I caught the issue yesterday evening on my other PC before it disappeared, and took a screenshot of the browser console. There's a lot of noise here, probably coming from other extensions, but here's one full page screenshot in case anything jumps out...

[gorhill]

I can't find related to uBO in that console output. There seems to be another extension causing all these errors/warning. What else do you have installed?

[Sejsel]

Had the issue with the 65.0.1 (64-bit) stable Windows build that was released yesterday.

After disabling "I am an advanced user" and purging all filter caches, then disabling and enabling the extension I no longer have the issue. I have re-enabled the advanced settings and everything seems to be working now.

When having this issue, I noticed there were no requests being made in the network tab of dev tools at all.

[uBlock-user]

Seems like it was a case of broken Nightly build/corrupted ubo storage.

[LinuxOnTheDesktop]

@uBlock-user I - and others, I believe - have the problem on regular ('release') Firefox.

[uBlock-user]

@LinuxOnTheDesktop Can you still reproduce this ?

[LinuxOnTheDesktop]

Yes, on UBO 1.18.4 on Linux. EDIT: I should say: intermittently.

[andyklimczak]

Experiencing this on Firefox Beta 66.0b4 (64-bit) on linux.
First pages will take forever to load. And will eventually load after a few minutes. There are no console error messages.
They instantly load if I go to about:addons and disable uBlock

[gorhill]

There is no point just saying you also have the issue, please also provide what is asked above: browser console error, new profile, other extensions interfering, etc. That the issue disappears when disabling uBO does not mean at all the issue lies with uBO, this needs to be further investigated. Since I can't reproduce, someone else will need to step up to investigate beyond reporting "me too".

[uBlock-user]

Updated to the latest Nightly and still cannot reproduce, those who can reproduce post a different set of repro steps for further investigation, otherwise this issue will not go anywhere beyond "me too".

@sciguyryan Were you able to reproduce on a clean profile ?

[LinuxOnTheDesktop]

Here are two sets of - somewhat overlapping - reports from the browser console. The output in report 1 (or some of it, anyway) was produced when, with Firefox (65.0, on Linux) open, I tried to open a Firefox tab, via Thunderbird, onto (so to speak) a github page. The output in report 2 was generated in the way way, including it being github that I was visiting, though this time the github page was this very page here. The second report was generated a few minutes after generating the first.

Report 1 (pastebin)
Report 2 (pastebin)
Here's some details of my Firefox configuration, too (also on Pastebin)

[gorhill]

I see nothing from uBO in there. I tried opening the current page from within a Thunderbird link, and it opened fine. Does it happen every time you try or just once in a while?

[gorhill]

The dev builds are always published in the Releases section.

[LinuxOnTheDesktop]

Here are some results with the beta. In all the scenarios that I describe browser.tabs.remote.autostart is true.

Windows, with Firefox 66.0

Loading this very webpage (viz., #416):

W1) when the browser was not previously open, works;
W2) when the browser was open already, works.

Linux, with Firefox 65.0.1 (version 66 hasn't arrived on my distro - Mint - yet)

Loading this very webpage:

L1) when the browser was not previously open, works;
L2) when the browser was open already, hangs,

I find further

L2') that 2 happens even when catchStorageAPI is set to browser.storage.local

and

L2'') 2 happens even when catchStorageAPI is set to browser.storage.local and when I use the release - not beta - version of the AddOn.

[LinuxOnTheDesktop]

Update: Linux, with Firefox 66 (version 66 just arrived), with catchStorageAPI unset

• when the browser was not previously open, works;
• when the browser was open already, works.

[gorhill]

When you say "works" on FF v66, this is with 1.18.11b0 only? Or is uBO's version unimportant?

[LinuxOnTheDesktop]

Upon further testing, I find that there is no problem with FF 66, on Linux, with either the beta version of UBO or with the release version of UBO, and without having to set the advanced options switch. So, in sum, it seems that Firefox 66, on its own, has solved the problem on both Platforms (Linux and Windows).

[ctjhoa]

FYI, I also got the same exact issue (infinite loading on any page).
Here is my configuration impacted by the issue:

• OS: Archlinux
• Firefox: 66.0.1 (64-bit)
• Firefox settings: browser.tabs.remote.autostart: true
• Ublock origin: 1.18.6
• Ublock advanced settings: cacheStorageAPI: unset

Modifying Ublock advanced settings cacheStorageAPI from unset to browser.storage.local fix the issue.

I did some tests on other configurations I have.

Configurations which work perfectly fine:
My windows:

• OS: Windows 10
• Firefox: 66.0.1 (64-bit)
• Firefox settings: browser.tabs.remote.autostart: true
• Ublock origin: 1.18.6
• Ublock advanced settings: cacheStorageAPI: unset

and my other arch:

• OS: Archlinux
• Firefox: 65.0.2 (64-bit)
• Firefox settings: browser.tabs.remote.autostart: true
• Ublock origin: 1.18.6
• Ublock advanced settings: cacheStorageAPI: unset

My filters & basic settings are the same across all my configurations.

[GerhardGitHub]

We have the same issue since update to Firefox Version 66.0 a few days ago
in combination with browser.tabs.remote.autostart: false

I made the experience that the Problem only appears when starting FF 66.0 with uBlock active.

If FF ist up running and Ublock is deactivated und instantly reactivated again in AddOns Configuration (not the uBlock-GUI), all pending pages load immediatly und the issue is gone until the next restart of FF
with Ublock active.
Some behavior with different UBlock Verions and unrelated to cacheStorageAPI: unset
or otherwise.

My guess is, the problem is related to the initializing procedure of uBlock and FF 66.0
that leaeds to some kind of deadlock condition.

Additional odd behavior is, that in some cases (not reproducable), the filter lists are
outdated even if they had been reloaded some short time before and wont update atuomatically .

[GerhardGitHub]

Just got FF 66.01
no issue even with FF-Setting browser.tabs.remote.autostart: false
and uBlock-Setting cacheStorageAPI: unset

[uBlock-user]

browser.tabs.remote.autostart: false

that breaks new tab page on FF 68, beware of that

[agentjsp]

The add-on seems to work for me without any of the workarounds. I'm on 67 Beta 4 though. I'm guessing the Firefox devs did something in 66.0.1/67 beta after the release of 66 that fixed it?

Apparently @ctjhoa got the issue even on 66.0.1 though, so I'm not sure.

[ixcat]

ff 66.0.1 osx
had the issue; browser.tabs.remote.autostart->true fixes the 'broken tab restart' issue;
did uninstall/reinstall ublock test without (ever) adjusting cachestorage api.

[vtpoet]

Desktop: Cinnamon 4.0.10 Distro: Linux Mint 19.1 Tessa
firefox: Installed: 66.0.1+linuxmint1+tessa

Just reporting if it's helpful. I've also been having this issue.

Firefox settings: browser.tabs.remote.autostart: true
uBlock Origin v1.18.12
Ublock advanced settings: cacheStorageAPI: unset

The only solution that seems to work on my system is to turn off ublock, from the addons page, and turn it back on.

[gorhill]

Firefox settings: browser.tabs.remote.autostart: true

What is your value for extensions.webextensions.remote?

[vtpoet]

Hi. The value is set to true.

[gorhill]

@vtpoet Did you restore a backed file with uBO 1.18.12? (or a recent uBO dev build)

[vtpoet]

No I didn't. Not smart enough to do that sort of JuJitsu. I saw that others had had success stopping and restarting, and tried that. Prior to that, I did disable all other addons, adding them back one by one, but none of that helped with Ublock.

[gwarser]

https://old.reddit.com/r/firefox/comments/b6yyx4/caution_when_using_latest_bleachbit_22_release/

Caution when using latest Bleachbit (2.2) release

I was unable to connect to any website using Firefox following a cleaning with the latest bleachbit update...

[xuhcc]

I have similar problem with uBlock. On my machine it always occurs on a first start of Firefox. Browser freezes for 2-3 minutes and only after that all tabs start loading. If I close browser and then reopen, it loads quickly. After reboot it freezes again.

OS: ArchLinux
Firefox: 66.0.2
uBlock: 1.18.14
cacheStorageAPI workaround: didn't help

At previous FF version (65) I had similar problem with another extension, IPFS companion (here's my bug report: ipfs/ipfs-companion#655). I tried to find out what part of code caused freeze and it seemed to be browser.webRequest.onBeforeRequest.addListener(onBeforeRequest, { urls: ['<all_urls>'] }, ['blocking']), but at this point of investigation freeze started to occur intermittedly so I gave up. After updating to FF66 something changed and now uBlock causes exactly the same freeze on a first start while IPFS companion works fine. All of it suggests that at least in my case the problem is with Firefox itself.

[doxxx]

Pages are never loading for me with uBlock Origin 1.18.14 on Firefox 67.0b6 on Windows 10 Enterprise 1803.

• The problem disappears when I disable the addon.
• The problem does not go away when I simply disable uBlock for a site.
• The problem occurs when only uBlock Origin is enabled.

I turned on debugging for the addon and found the following in the addon's console log:

Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. background.js:18709
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. storage.js:100
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. storage.js:261
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. background.js:18709
TypeError: Argument 1 of PrecompiledScript.executeInGlobal is not an object. ExtensionContent.jsm:490:25
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. background.js:18709
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. storage.js:100
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. storage.js:261
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. background.js:18709
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. storage.js:100
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. storage.js:261
Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. ExtensionUtils.jsm
DOMException: "The operation failed for reasons unrelated to the database itself and not covered by any other error code." cachestorage.js:230:29
Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. ExtensionUtils.jsm
TypeError: The expression cannot be converted to return the specified type.
Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. background.js:18709

I tried setting the cacheStorageAPI setting to browser.storage.local but it did not fix the problem. EDIT: My change to this setting did not appear to persist, so I'm unsure whether it actually took effect. I did click the Apply Changes button...

[gorhill]

This issue has become pointless, it's now just a melting pot of all sort of possibly unrelated issues. Many of these where caused by remote.autostart set to false. The others might be cause by specific configuration which would explain why the issue can't be reproduce by most, including me. The issue should be closed now as it's pretty much unactionable at this point, and whoever has a specific issue should open one with all the steps asked in the template being checked -- otherwise the issue will be closed. If it can't be reproduced by me and other volunteers, the assumption is that there is something specific on the user side which only hm can investigate.

[gorhill]

I turned on debugging for the addon and found the following in the addon's console log:

Unchecked lastError value: Error: UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. background.js:18709

There is no line 18709 in uBO's background.js, so such console log entry makes no sense to me.

[doxxx]

Yeah, I noticed that. My suspicion is that it's something in Firefox 67.0b6 because everything was working on Friday, then I accepted the pending Firefox update this morning and everything was broken.

I'll post a new issue once I've tried it with a new profile.

[doxxx]

So after I figured out how to create a new profile, I was able to verify that the problem does not occur in a new profile after installing uBlock. So something in my main profile is busted. I tried the Refresh Firefox feature and after reinstalling uBlock, I am unable to reproduce the problem.

So, TLDR: Refresh your Firefox profile.

[gwarser]

One more edge case: foreign files in storage directory (but not standard system files, they are handled now by Fx) will cause endless loading until uBO is closed.

However, this line will be shown in browser console:

Quota Something (Text File) in the directory that doesn't belong!: ActorsParent.cpp:3905

---

One more case:

On Mac with "Cookie" app storage may be corrupted: https://old.reddit.com/r/uBlockOrigin/comments/b4vzaf/i_am_an_advanced_user_is_disabled_on_quit_in/ejpewhz/

---

https://bugzilla.mozilla.org/show_bug.cgi?id=1543880

[gorhill]

foreign files in storage directory

But is it something uBO can and/or has to handle? The failure seems to be Firefox-side.