uBlockOrigin / uBlock-issues

This is the community-maintained issue tracker for uBlock Origin
https://github.com/gorhill/uBlock
928 stars 78 forks source link

No page can load while uBlock is active #3217

Closed j36e closed 1 day ago

j36e commented 5 months ago

Prerequisites

I tried to reproduce the issue when...

Description

https://github.com/uBlockOrigin/uBlock-issues/assets/147976004/5633061e-c972-4d8e-87d6-497ac5664927

Pages won't load with UBO enabled but everything works fine when it's off. Everything was fine a couple of hours ago and yes I did reboot my computer. Sorry for the bad video quality my laptop is slow

A specific URL where the issue occurs.

https://github.com/uBlockOrigin/uBlock-issues/issues/new?assignees=&labels=&projects=&template=bug_report.yml

Steps to Reproduce

  1. [Enable UBO]
  2. [Try to load a page]

Expected behavior

The page to load

Actual behavior

It did not :(

uBO version

1.57.0

Browser name and version

Chromium (chromium-123.0.6312.86_1)

Operating System and version

Void linux

j36e commented 5 months ago

The first tab title seemed to load but it was probably cached since I tried the same query minutes before

gorhill commented 5 months ago

When you click uBO's "background.html" link in chrome://extensions/, this opens the browser tools for uBO. Can you see something reported in the console pane?

j36e commented 5 months ago

Lmao the addon wouldnt do anything when I clicked on it so I reinstalled and it's all working now sorry for the stupid issue report

gorhill commented 5 months ago

We had other reports of such behavior, so I don't consider this invalid. Problem is that so far I have been unable to investigate further since the issue disappear upon reinstall.

@j36e Do you think that uBO had just updated to 1.57.0 before the issue occurred?

ghost commented 5 months ago

I faced the same issue too. But in my case, after updating to 1.57.0, i lost all saved filters too and uBO was completely reset to default. allReadyAfter after this incident was over 80k ms. The dashboard was completely blank after this, restarting my browser did fix it, but had to continue from a old backup. Browser used: Edge Possible in https://github.com/uBlockOrigin/uBlock-issues/issues/3219, OP did face something similar (chromium used)

stephenhawk8054 commented 5 months ago

@voidlyvidevoid Can you do the steps described in this: https://github.com/uBlockOrigin/uBlock-issues/issues/3217#issuecomment-2063911578

garry-ut99 commented 5 months ago

j36e : No page can load while uBlock is active j36e : Pages won't load with UBO enabled j36e : Possible in https://github.com/uBlockOrigin/uBlock-issues/issues/3219, OP did face something similar (chromium used)

Also possible you encountered the same like here:


voidlyvidevoid : allReadyAfter after this incident was over 80k ms

In this one 85k ms too:

also you can read (if you didn't see them before):

ghost commented 5 months ago

Tho this happend a few weeks ago when the update was pushed. Never had anything over 15k ms except when this occured. I get 12-15k ms consistently in FF and Edge and I take the blame for that as I have nearly 500k+ network filters (mostly badware, malware and anti-paywalls) Also, something maybe unrelated, Edge takes a good 30s after restart to load anything.(this is with and without suspendUntilListsAreLoaded: true) image

stephenhawk8054 commented 5 months ago

@voidlyvidevoid Can you click on uBO icon > 💬 Report button > scroll to the bottom > click on Troubleshooting Information and copy paste it here?

ghost commented 5 months ago

I usually don't find them these high, but 12-15k ms and some 3k is mostly consistent. This is immediately after a restart, with 12 tabs open from previous session. (Using hard mode,with block large media) Other extensions: Webtime tracker and Dark reader

uBlock Origin: 1.57.2
Chromium: 124
filterset (summary):
 network: 544853
 cosmetic: 260618
 scriptlet: 53426
 html: 0
listset (total-discarded, last-updated):
 added:
  https://gitlab.com/magnolia1234/bypass-paywalls-clean-filters/-/raw/main/bpc-paywall-filter.txt: 1065-0, 9d.14h.27m
  https://o0.pages.dev/Pro/adblock.txt: 155647-18753, 6d.21h.26m
  https://raw.githubusercontent.com/AdguardTeam/cname-trackers/master/data/combined_disguised_trackers_justdomains.txt: 69497-0, 13h.34m
  https://raw.githubusercontent.com/DandelionSprout/adfilt/master/Alternate versions Anti-Malware List/AntiMalwareDomains.txt: 21187-7502, 8h.44m
  https://raw.githubusercontent.com/DandelionSprout/adfilt/master/Dandelion Sprout's Anti-Malware List.txt: 85890-1918, 8h.43m
  https://raw.githubusercontent.com/DandelionSprout/adfilt/master/LegitimateURLShortener.txt: 2621-0, 9h.44m
  https://raw.githubusercontent.com/gwarser/filter-lists/master/lan-block-strict.txt: 54-0, 11d.6h.44m
  https://raw.githubusercontent.com/hagezi/dns-blocklists/main/adblock/ultimate.txt: 187296-102175, 15h.34m
  https://raw.githubusercontent.com/liamengland1/miscfilters/master/antipaywall.txt: 2098-36, 8h.43m
  https://raw.githubusercontent.com/voidlyvidevoid/filterlist1/main/filterlist.txt: 4-0, 1m
  https://someonewhocares.org/hosts/ipv6/hosts: 23338-23337, 16h.35m
  adguard-generic: 80958-5587, 1d.15h.33m
  [23 lists not shown]: [too many]
 default:
  user-filters: 23-0, never
  ublock-filters: 37577-3878, 1m Δ
  ublock-badware: 8320-919, 1m Δ
  ublock-privacy: 832-101, 1m Δ
  ublock-unbreak: 2256-1, 1m Δ
  ublock-quick-fixes: 274-25, 1m Δ
  easylist: 86419-34227, 1m Δ
  easyprivacy: 50793-37792, 1m Δ
  urlhaus-1: 13070-111, 15h.34m
  plowe-0: 3739-3518, 8d.16h.55m
filterset (user): [array of 23 redacted]
trustedset:
 added: [array of 6 redacted]
switchRuleset:
 added: [array of 15 redacted]
 removed:
  no-large-media: behind-the-scene false
hostRuleset:
 added: [array of 70 redacted]
userSettings:
 advancedUserEnabled: true
 largeMediaSize: 250
 suspendUntilListsAreLoaded: true
hiddenSettings:
 filterAuthorMode: true
supportStats:
 allReadyAfter: 29598 ms (selfie)
 maxAssetCacheWait: 10212 ms
 cacheBackend: indexedDB
popupPanel:
 blocked: 12
 no-large-media: true
 network:
  github.com: 12

image

stephenhawk8054 commented 5 months ago

@voidlyvidevoid This gitlab user is removed by Gitlab already so its filter list cannot be updated: https://gitlab.com/magnolia1234/bypass-paywalls-clean-filters/-/raw/main/bpc-paywall-filter.txt

You are using a heavily modified configuration so we cannot pinpoint what causes the issue. Backup and reset to default settings and test again. Then restore your configuration one-by-one and see which one is causing issue.

Anyways, since you can access uBO's dashboard, I don't think your issue is the same as this issue. It's more similar to this: https://github.com/uBlockOrigin/uBlock-issues/issues/1865 so please continue in that thread instead. But do what I said above first.

stephenhawk8054 commented 5 months ago

@gorhill However, I'm thinking maybe some user-removed gitlab links could be related to OP's issue? From the screenshot, I see gitlab.com/users/sign_in link in the error line instead, which is a redirection from https://gitlab.com/magnolia1234/bypass-paywalls-clean-filters/-/raw/main/bpc-paywall-filter.txt

gorhill commented 5 months ago

I expect over half a million network filter is going to cause longer delay at launch, although 25s seems high, it's not a configuration I test often. It could be a storage issue, in which case it might be useful to force the indexedDB to be re-created, a backup/restore should do this.

garry-ut99 commented 5 months ago

voidlyvidevoid: allReadyAfter after this incident was over 80k ms. The dashboard was completely blank after this, restarting my browser did fix it

It's normal that uBO's dashboard page is blank/white while uBO is not ready (while uBO toolbar icon is yellow), unless you mean that it was still white/blank even after uBO's toolbar icon was not yellow anymore - but in such case you wouldn't be able to access and read allReadyAfter 80k, so I assume it was blank/white only while uBO was not ready.

gwarser commented 5 months ago

@garry-ut99 there is a timeout for the badge - it will be shorter than his 80 seconds.

gorhill commented 5 months ago

there is a timeout for the badge

The countdown starts when uBO is all ready if I remember correctly.

garry-ut99 commented 5 months ago

there is a timeout for the badge - it will be shorter than his 80 seconds.

I'm not talking about a badge, but about an icon, they are two separate things, the yellowish icon has no timeout, and as for the the yellowish badge, like gorhill mentioned, its countdown starts after uBO is ready, like already mentioned 2 times in Wiki:

https://github.com/gorhill/uBlock/wiki/Toolbar-icon : The yellowish badge ! will persist once uBO is ready to filter properly (...) https://github.com/gorhill/uBlock/wiki/Toolbar-icon#important-note : The sticky yellowish badge once uBO is fully loaded

also worth to mention another difference between the yellowish icon and the yellowish badge: the yellowish badge doesn't prevent uBO and dashboard from working, which means uBO and dashboard are accessible after yellowish icon disappears, even if yellowish badge is still here, because the yellowish badge servers only as an additional non-blocking warning and counter of unprocessed browser requests.

Avellea commented 5 months ago

Popping in to say I have the same issue on the latest versions of Chrome and Thorium. I cannot access the uBO dashboard or any websites. There is nothing reported in the uBO DevTools console either.

Uninstalling and reinstalling the extension does seem to fix the issue.

stephenhawk8054 commented 5 months ago

@Avellea Do you remember you were using / enabling any additional filter lists (bypass paywall...)?

Avellea commented 5 months ago

@Avellea Do you remember you were using / enabling any additional filter lists (bypass paywall...)?

I do not use any custom filter lists at all.

garry-ut99 commented 5 months ago

"Popping in" is appreciated and useful to know how many users have the same problem, and how big is the problem, but we need more details to help:

I cannot access the uBO dashboard or any websites.

When has it happened exactly?:

Has been uBO's icon yellowish as per https://github.com/uBlockOrigin/uBlock-issues/wiki/Toolbar-icon while you were unable to access dashboard?

Uninstalling and reinstalling the extension does seem to fix the issue.

Are you able to reproduce the issue again or it doesn't occur anymore. If you could reproduce it again it would be helpful for us to diagnose it.

What is your OS and version of uBO.

Avellea commented 5 months ago

"Popping in" is appreciated and useful to know how many users have the same problem, and how big is the problem, but we need more details to help:

Apologies, let me clear this up.

iMarbot commented 5 months ago

Started experiencing this yesterday with uBlock Origin development build 1.57.3.6. I'm sorry but I don't know whether it happened after a browser or extension update. It happened after I closed Chrome entirely and then re-opened it, everything was refusing to load. The icon was yellow with the exclamation mark. Also, the extension was using almost 100 CPU in Chrome's task manager.

image

Disabling the extension leads to pages instantly loading, without even needing to refresh or restart their loading.

Chrome version: 124.0.6367.91 (Official Build) (64-bit) (cohort: M124 Rollout)

I have not tested cleaning the extension data or re-installing it as I didn't want to lose my settings but also in case I can help reproduce the issue.

I also have uBlock Origin 1.57.0 installed (not running at the same time, obviously) which works fine on the exact same browser environment. The settings are a little different but I can't even open the uBlock popup or settings in the dev build because it's just hanging on something with that high CPU usage.

Let me know if there's anything I have missed or can do to help isolate the issue.

stephenhawk8054 commented 5 months ago

@iMarbot Can you do this step: https://github.com/uBlockOrigin/uBlock-issues/issues/3217#issuecomment-2063911578 ?

iMarbot commented 5 months ago

@iMarbot Can you do this step: #3217 (comment) ?

Nope, it's empty. However, I'm not sure if it outputs something before I'm able to open the window with the console.

stephenhawk8054 commented 5 months ago

@iMarbot Which OS are you using?

Can you go to chrome://flags/#enable-tls13-kyber, disable TLS 1.3 hybridized Kyber support, restart the browser (make sure that all instances of chrome is turned off in Task Manager) and test again if the issue still occurs?

WesselKroos commented 5 months ago

I had this yesterday with the default extension settings. Eventually got it fixed after doing these steps:

I guess a filter list was causing this problem for me or something got corrupted in a filter list? I don't know which one specifically.

garry-ut99 commented 5 months ago

iMarbot : However, I'm not sure if it outputs something before I'm able to open the window with the console.

It will, but only in uBO dev, because debugging information to console output is enabled by default only in uBO dev ( in uBO stable can be enabled manually via a flag: https://github.com/gorhill/uBlock/wiki/Advanced-settings#consoleloglevel ).

iMarbot : Nope, it's empty.

In which version of your uBO it is empty: 1.57.3.6 (dev channel) or on 1.57.0 (stable channel)?

If it's empty for you on uBO dev, then this is definitely abnormal behavior - it would indicate that the issue happens at very early stage of uBO initialization, as soon as uBO is enabled, preventing uBO even from debugging information to console output.

iMarbot commented 5 months ago

Which OS are you using?

Can you go to chrome://flags/#enable-tls13-kyber, disable TLS 1.3 hybridized Kyber support, restart the browser (make sure that all instances of chrome is turned off in Task Manager) and test again if the issue still occurs?

Edition     Windows 11 Home
Version     23H2
Installed on    ‎16/‎06/‎2023
OS build    22635.3566
Experience  Windows Feature Experience Pack 1000.22700.1007.0

I was going to report back with good news initially, disabling that flag and relaunching chrome fixed the problem. However, after resetting it back to default and then launching the browser again, the issue did not return. I'm not sure if that is expected or not. And to top it off, when I relaunched chrome, it updated to version 124.0.6367.119 (Official Build) (64-bit) (cohort: Stable), so potentially that might've fixed it instead.


In which version of your uBO it is empty: 1.57.3.6 (dev channel) or on 1.57.0 (stable channel)

I checked both and both were empty, but obviously I reported back about the dev build as that's the one that was experiencing the issue. After the issue went away because one of the above reasons (or something else, I guess?), the console has a bunch of debugging information in it.

Maxr1998 commented 5 months ago

Had this happen to me on Vivaldi (6.7.3329.24) on Linux (Arch) this morning.

Troubleshooting information uBlock Origin: 1.57.0 Chromium: 124 filterset (summary): network: 145821 cosmetic: 161447 scriptlet: 33960 html: 0 listset (total-discarded, last-updated): added: https://filters.adtidy.org/extension/ublock/filters/14.txt: 78408-4449, 4d.9h.30m fanboy-cookiemonster: 50983-204, 1d.11h.4m fanboy-thirdparty_social: 68-0, 1d.23h.5m ublock-annoyances: 6966-28, 2m Δ default: user-filters: 15-0, never DEU-0: 7439-1, 12h.15m easylist: 86828-469, 2m Δ easyprivacy: 50856-799, 2m Δ plowe-0: 3735-0, 3d.10h.44m ublock-badware: 8505-0, 2m Δ ublock-filters: 37812-426, 2m Δ ublock-privacy: 881-2, 2m Δ ublock-quick-fixes: 261-5, 2m Δ ublock-unbreak: 2268-21, 2m Δ urlhaus-1: 12765-0, 12h.15m filterset (user): [array of 17 redacted] trustedset: added: [array of 36 redacted] switchRuleset: added: [array of 2 redacted] hostRuleset: added: [array of 1 redacted] userSettings: advancedUserEnabled: true cloudStorageEnabled: true hiddenSettings: [none] supportStats: allReadyAfter: 757 ms maxAssetCacheWait: 208 ms cacheBackend: indexedDB popupPanel: blocked: 21 network: github.com: 21

No pages would load, and CPU usage was very high. Restarting the browser multiple times didn't help. Found uBlock at 100% in the task manager (thanks to a hint in this reddit thread), after disabling the extension, CPU usage went down and pages would load again.

Re-enabling the extension caused the issue to return. I cleared the browser cache and restarted the browser once more, re-enabled the extension, but the issue persisted. Disabled and re-enabled the extension again, and it suddenly started to work. Unfortunately, I don't see anything in the background.html console.

garry-ut99 commented 5 months ago

Unfortunately, I don't see anything in the background.html console.

Because as already explained 2 comments above ( in https://github.com/uBlockOrigin/uBlock-issues/issues/3217#issuecomment-2088560489 ) : the stable version of your uBO (1.57.0) doesn't output anything to the console by default, until you manually set a flag, which I suppose you didn't.

Besides, a new verison of uBO has just been released: https://github.com/gorhill/uBlock/releases/tag/1.57.3b7 which contains a test fix: https://github.com/gorhill/uBlock/commit/c098eb8625.

gorhill commented 5 months ago

Regarding the above commit: So far I have been unable to observe the telltale code path being triggered after days (by setting a breakpoint) -- though the browser was not in heavy use, that code path I gather could have been visited when a selfie is generated, but no luck so far. To increase likelihood I have enabled many other stock lists.

Whoever with JS dev skill is suffering an issue of broken uBO, a breakpoint at https://github.com/gorhill/uBlock/blob/1.57.2/src/js/s14e-serializer.js#L744-L745 being triggered at launch time could confirm the issue is related to the above commit.

Ovear commented 4 months ago

I encountered the same problem on Arch Linux after upgrading the system today.

uBlock will consume 100% cpu once trying to load any page (and prevent page from loading), same situation happened even in incognito mode.

Turn off uBlock makes page to load immediately and CPU dropped to normal level. Not observed any output in Console of uBlock's background page.

Before upgrading Chrome, this situation happened randomly with some pages stop loading but will work with a force close and open again. Not sure if it's related to this problem.

upgraded google-chrome (123.0.6312.122-1 -> 124.0.6367.155-1)

The solution to this (currently) also weird, I disabled Enable my custom filters, and everything back to work, even I enable it again after that.

Maxr1998 commented 4 months ago

Because as already explained 2 comments above ( in https://github.com/uBlockOrigin/uBlock-issues/issues/3217#issuecomment-2088560489 ) : the stable version of your uBO (1.57.0) doesn't output anything to the console by default, until you manually set a flag, which I suppose you didn't.

Nope, I must have missed that comment, and thus didn't set that flag. I apologize for the oversight. I haven't been able to reproduce the issue anymore since then, but I'll remember it if I notice it again.

usermyname12 commented 4 months ago

It occurred to me 1 week before and i had to reinstall. It did today as well, in incognito (i have it enabled there). I can bypass it by searching something instead of pasting a link or clicking on a bookmark, then everything works fine. Before it does not consume cpu or gets stuck, only if i try to go directly to a site it starts using a core to 100% and ubo interface freezes. Also it has to be a blank page in the beginning (obviously in incognito it does). Performance recording does not work as it gets stuck when it matters. Also incognito is good for quick testing as i have learned.

Procyon-b commented 4 months ago

I have an installation that is blocked like some users are reporting.

Chrome 109 (windows 8.1, so no choice) If it can be useful to use it for tests feel free to ask. (I won't be 7/7 24/24 behind the screen)

I'm currently using this profile with uBO 1.57.3.8 disabled, and with beta 1.57.6 side-loaded.

The symptoms were/are: no access to any site (time-out) even on my local network. I though it was the wifi router. Tried with FF. It worked partially (could not access wifi router). Restarted both browsers. Same issues. Rebooted. "Looked" better but uBO's icon stayed yellow with "!". High CPU (didn't investigate further). Disable/enable uBO. Icon is red. Able to open the popup, but as soon as I try to access a site, uBO is unresponsive. Disable/enable. Open uBO dashboard. Export settings (already had backups).

Tried again right now (after uBO sideloaded) : 1.57.3.8 is still in distress.

I have backuped the chrome user dir. So hopefully I can recreate the problem if one of my actions solves the issue.

iMarbot commented 4 months ago

@Procyon-b maybe test the stuff that was suggested to me; checking for console output in background.html (if on dev channel) and setting chrome://flags/#enable-tls13-kyber to disabled.

Procyon-b commented 4 months ago

@iMarbot I don't really care about solving my issue. It's already solved. It's just to inform that I have an installation that can be used to debug the root of the issue.

iMarbot commented 4 months ago

I don't really care about solving my issue. It's already solved. It's just to inform that I have an installation that can be used to debug the root of the issue.

And testing both of those things and seeing whether they fix the issue or not (or have information that might point to what the issue is) should help narrow down the cause. But I'll leave that to the uBlock devs.

gorhill commented 4 months ago

I have an installation that can be used to debug the root of the issue.

Is it something you would share (zip file) with me to see if I can reproduce on my side?

Procyon-b commented 4 months ago

@gorhill yes , of course. That's why I mentionned it.

gorhill commented 4 months ago

Thanks, you can send the file to rhill at raymondhill dot net.

Procyon-b commented 4 months ago

Is there a size limit by email ? Right now my complete profile (without the various cache dirs) is 124Mb (.rar). I'll try removing unecessary things (other extensions) as long as uBO is still broken. Do you need the non-profile files too (the ones not in a profile dir) ?

gorhill commented 4 months ago

I would just need what is related to uBO, nothing else. Maybe search for uBO's extension id (cjpalhdlnbpafiamejdnhcphjbkeiagm) and put all the matching folders in a zip file?

Procyon-b commented 4 months ago

no prob.

Procyon-b commented 4 months ago

It will be cgbcahbpdhpcegmbfconppldiemgcoii since the problem is with the beta version (just after updating x.6 to x.8)

gorhill commented 4 months ago

I received 3 emails, it looks they all contain the same attachments?

Procyon-b commented 4 months ago

It's a 3 parts rar attachment (my provider doesn't allow files bigger than 20Mb) The 4th email is bouncing (no attach, text only)

Procyon-b commented 4 months ago

File names should be:

Default.part1.rar  18,000,000 bytes
Default.part2.rar  18,000,000 bytes
Default.part3.rar  12,210,005 bytes

rar.exe should recontruct while decompressing simply by giving it the 1st file

gorhill commented 4 months ago

I can reproduce 100 CPU% at launch if I open a webpage once uBO is ready. The issue seems to be that the selfie is "corrupted". I use quotes because it seems valid, but one part of the selfie (which is saved in multiple parts to indexedDB) seems to not correspond to the rest, as if an older version of that part was used along with the other up to date parts. I still need to investigate, and think of a way to detect such bad state.