Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kiwi browser #3198

Closed
7 tasks done
MusicaFM opened this issue Apr 7, 2024 · 22 comments
Closed
7 tasks done

Kiwi browser #3198

MusicaFM opened this issue Apr 7, 2024 · 22 comments
Labels
feedback needed need more feedback from the issue submitter

Comments

@MusicaFM
Copy link

MusicaFM commented Apr 7, 2024

Prerequisites

  • I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
  • This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
  • I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
  • The issue is not present after disabling uBO in the browser.
  • I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

  • uBO is the only extension.
  • using a new, unmodified browser profile.

Description

A veces se bloquea en Kiwi Browser y no me carga ninguna web se queda cargando, abro para configurar Ublock y de queda en blanco tengo que deshabilitar para poder entrar en páginas webs y si lo activo de nuevo puede que valla bien o no

A specific URL where the issue occurs.

None

Steps to Reproduce

Se bloquea en Kiwi browser al inicia el navegador, la primera vez funciona vien, pero cargas de nuevo u otra web y se bloquea

Expected behavior

Deberia ir como siempre

Actual behavior

Se bloquea en Kiwi browser, las demás extensiones funcionan correctamente

Configuration

uBlock Origin: 1.57.0
Chromium Mobile: 124
filterset (summary):
 network: 334928
 cosmetic: 373266
 scriptlet: 56698
 html: 0
listset (total-discarded, last-updated):
 added:
  adguard-generic: 80490-7589, 16h.18m
  adguard-spyware-url: 1492-107, 16h.17m
  adguard-spyware: 102336-32419, 16h.18m
  block-lan: 61-0, 5d.17h.20m
  curben-phishing: 14193-4, 3h.58m
  adguard-cookies: 29175-80, 16h.18m
  ublock-cookies-adguard: 1106-0, 5d.17h.20m
  fanboy-cookiemonster: 50759-3950, 5d.16h.33m
  ublock-cookies-easylist: 1106-1106, 5d.17h.20m
  adguard-social: 22753-874, 16h.18m
  fanboy-social: 15849-29, 5d.16h.33m
  fanboy-thirdparty_social: 68-0, 5d.16h.33m
  [44 lists not shown]: [too many]
 default:
  user-filters: 2-1, never
  ublock-filters: 37741-812, 13m Δ
  ublock-badware: 8341-15, 13m Δ
  ublock-privacy: 785-0, 13m Δ
  ublock-unbreak: 2245-5, 13m Δ
  ublock-quick-fixes: 224-0, 13m Δ
  adguard-mobile: 9234-171, 16h.16m
  easylist: 84380-1307, 13m Δ
  easyprivacy: 50455-1141, 13m Δ
  urlhaus-1: 8795-0, 13h.56m
  plowe-0: 3763-13, 5d.17h.21m
  spa-0: 4023-7, 13h.56m
  spa-1: 5447-187, 16h.17m
filterset (user): [array of 2 redacted]
switchRuleset:
 added: [array of 1 redacted]
userSettings: [none]
hiddenSettings: [none]
supportStats:
 allReadyAfter: 4628 ms
 maxAssetCacheWait: 1787 ms
 cacheBackend: indexedDB
@gwarser
Copy link

gwarser commented Apr 7, 2024

Try reducing number of filters (subscribed lists) - it's possible your device does not have enough memory when uBO parses and compiles all lists (Startup is slow allReadyAfter: 4628 ms). What device is this?

Kiwi is not supported #2791 (comment)

@MusicaFM
Copy link
Author

MusicaFM commented Apr 7, 2024

Xiaomi redmi note 11s

@gwarser
Copy link

gwarser commented Apr 7, 2024

6 or 8GB that is.

On my 6GB phone, Nightly, uBO dev, 140k network + 180k cosmetic filters, WebExtension process can take 3GB as per profiling.
1.5GB with default settings.
System shows 3.6 out of 6GB available when all apps are closed.

With 330k network + 370k cosmetic, maybe some stuff in background, out of memory situation is possible.

@stephenhawk8054
Copy link
Member

You enabled all regional filter lists?

@MusicaFM
Copy link
Author

MusicaFM commented Apr 7, 2024

Yes

@stephenhawk8054
Copy link
Member

Why? How many times do you visit Vietnamese and Thailand sites?

@MusicaFM
Copy link
Author

MusicaFM commented Apr 7, 2024

Never, but I activate it just in case

@stephenhawk8054
Copy link
Member

Don't do that. Just enable the lists of the languages you usually visit. The more lists you enable, worse performance and potential breakages can occur without any benefits.

@garry-ut99
Copy link

To OP: check whether:
-- the issue occurs with default settings with default lists only
-- occurs on Firefox Mobile

Al OP: compruebe si:
-- el problema se produce sólo con la configuración predeterminada con listas predeterminadas
-- ocurre en Firefox Mobile


On my 6GB phone, Nightly, uBO dev, 140k network + 180k cosmetic filters, WebExtension process can take 3GB as per profiling. 1.5GB with default settings. With 330k network + 370k cosmetic, maybe some stuff in background, out of memory situation is possible.

A joke or what, the values (1.5GB and 3GB) you've provided are insane, maybe you've confused real memory usage with virtual memory:

I've checked on Firefox Nightly Mobile and Kiwi Browser: uninstalled Firefox Nightly Mobile, then installed it again, then installed uBO, then loaded 900k filters config, all while monitoring RAM usage, and RAM usage has incerased by only additional 300 MB for a while, then later has decreased much.

@gwarser gwarser closed this as not planned Won't fix, can't repro, duplicate, stale Apr 8, 2024
@gwarser gwarser added the feedback needed need more feedback from the issue submitter label Apr 8, 2024
@garry-ut99
Copy link

These gigabytes in FF profiler are bogus / virtual, I get similiar result to yours in FF profiler, but Android built-in system RAM monitor + built-in app RAM monitor + also 2 different 3rd party system RAM monitor apps show only 300-400 MB real RAM usage incerase for a while when loading high number of filter lists.

@gwarser
Copy link

gwarser commented Apr 8, 2024

Good news then. I recall seeing such high numbers before on desktop, I will need to check if it was discussed, check my test method and try it again to make sure.

@gwarser
Copy link

gwarser commented Apr 8, 2024

I'm not convinced for now. Memory fluctuates a lot. When I set my system monitor to higher refresh rate (0,1s), I see the memory increasing by nearly 1GB. On my default setting (2s), it's unnoticeable.


On desktop.

@gorhill
Copy link
Member

gorhill commented Apr 8, 2024

These gigabytes in FF profiler are bogus / virtual

On desktop, wasm causes increased virtual memory usage, maybe it's the same thing in android.

@garry-ut99
Copy link

garry-ut99 commented Apr 8, 2024

On desktop I get 600-700 MB RAM usage incerase for a while (all filter lists enabled in uBO, tested with 0,5s and 0,1s refresh intervals, FF 124, Windows), so it's 2x more than on Android, but still far away to these bogus / virtual gigabytes from FF profiler.

(Updated: Have tried few more times and sometimes I get 800-900 MB, but not more. )

@gwarser
Copy link

gwarser commented Apr 8, 2024

Profiler has a "Native Allocations" feature, which should report more real data. But still only sampling. https://profiler.firefox.com/docs/#/./memory-allocations Sadly crashes for me on Linux and I cannot allocate enough memory to VM to not see swapping.


I was able to capture profile under Win after reducing the number of subscribed lists. For some reason, the recording does not capture the first few dozen seconds.

Firefox 2024-04-08 22.42 profile.json.gz

@garry-ut99
Copy link

garry-ut99 commented Apr 9, 2024

With "Native Allocations" ticked, it freezes/crashes for me as well in native Windows, so it crashes in both native Windows and Linux, it freezes/crashes whole browser to the point I'm unable to stop Profiler, it forces me to kill the browser.

@gwarser
Copy link

gwarser commented Apr 9, 2024

Most of the allocations are from JSON.stringify and Array.prototype.join. It seems to me that there are a lot of calls to these functions, so this can explain both, the memory usage - if GC is not catching up, and the profiler being wrong - by capturing more samples with allocation than with deallocation.


Definitely not virtual memory. I can capture some of this in about:memory reports - in explicit allocations, heap and js runtime.

@garry-ut99
Copy link

Do any external RAM monitoring apps outside browser confirm your FF Profiler or about:memory results like 1,5GB or 3GB, I tried several of them, including setting 100ms or even 50ms sampling interval, and none of them have confirmed values reported by FF.

@gorhill
Copy link
Member

gorhill commented Apr 9, 2024

Most of the allocations are from JSON.stringify and Array.prototype.join

This is from parsing/compiling filter lists, not unexpected. Lists are compiled once in a while.

@alexandreraufast
Copy link

I had same problem on latest Kiwi Browser. Uninstalling-reinstalling uBO extension did work.
I also had a lot of custom filters, copied from my computer.

@ChowMein47
Copy link

ChowMein47 commented May 1, 2024

I had same problem on latest Kiwi Browser. Uninstalling-reinstalling uBO extension did work. I also had a lot of custom filters, copied from my computer.

The best solution is uninstall Kiwi Browser, install Firefox or Waterfox. Fyi, Edge for Android now support extension including uBO (still beta)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback needed need more feedback from the issue submitter
Projects
None yet
Development

No branches or pull requests

7 participants