-
Notifications
You must be signed in to change notification settings - Fork 81
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
Comments
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 Kiwi is not supported #2791 (comment) |
Xiaomi redmi note 11s |
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. With 330k network + 370k cosmetic, maybe some stuff in background, out of memory situation is possible. |
You enabled all regional filter lists? |
Yes |
Why? How many times do you visit Vietnamese and Thailand sites? |
Never, but I activate it just in case |
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. |
To OP: check whether: Al OP: compruebe si:
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. |
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. |
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. |
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. |
On desktop, wasm causes increased virtual memory usage, maybe it's the same thing in android. |
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. ) |
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. |
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. |
Most of the allocations are from Definitely not virtual memory. I can capture some of this in about:memory reports - in explicit allocations, heap and js runtime. |
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. |
This is from parsing/compiling filter lists, not unexpected. Lists are compiled once in a while. |
I had same problem on latest Kiwi Browser. Uninstalling-reinstalling uBO extension did work. |
The best solution is uninstall Kiwi Browser, install Firefox or Waterfox. Fyi, Edge for Android now support extension including uBO (still beta) |
Prerequisites
I tried to reproduce the issue when...
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
The text was updated successfully, but these errors were encountered: