Active page background process gets killed in less than a minute

[CHEYCKIT]

As title says, related to issue #447 where it was mentioned at first before the conversation switched to another topic

I have 12gb of RAM, yet as I'm typing this on my phone in WebLibre, if I were to leave the app to open twitter and scroll for less than a minute, going back to WebLibre this active GitHub page would reload. That's not normal behaviour, chrome for example stays a while in the background and the active page doesn't reload even if i were to open 10 different apps or worked on something else for 30 minutes, this isn't possible with WebLibre and I'm far from running out of memory on my phone.

Initially I thought it was my phone who was aggressively killing WebLibre's process (Xiaomi 17) but no I only have this issue with WebLibre and no other app

See video in following post

[CHEYCKIT]

The WebLibre active page process doesn't get killed because of some sort of timer (I tested this) so it seems like a memory allocation issue

Screenrecorder-2026-06-30-23-48-00-427.mp4

[FaFre]

please add device/os info and app version

[CHEYCKIT]

please add device/os info and app version

Xiaomi 17
Android 16
0.20 alpha 11

[FaFre]

Mhm do you have any pass playing with battery optimization or optimizations in general? Please try some stuff from here as well: https://dontkillmyapp.com/xiaomi

[CHEYCKIT]

Mhm do you have any pass playing with battery optimization or optimizations in general? Please try some stuff from here as well: https://dontkillmyapp.com/xiaomi

You're right, it was the battery optimization setting, problem solved

[CHEYCKIT]

Yeah sorry @FaFre problem not solved, so yes putting the battery settings on "no restrictions" helped a bit but the process still gets killed way too easily compared to Chrome and my Chrome app is on Battery Saver mode whereas WebLibre is on No Restrictions mode, so the issue is not coming from the fact that I have a Xiaomi.

Also tried with both the latest alpha and the stable from play store, and the issue persists

Here's a 1m video of Chrome vs WebLibre after watching a few videos on youtube, which is the easiest way for anyone to replicate this.

The previous post video can't be replicated when on No Restrictions, so again there's an improvement just not a good enough one

Screenrecorder-2026-07-02-10-06-22-703_compressed.1.mp4

The link you shared @FaFre also talks about app pinning and neither Chrome nor WebLibre were pinned so they're on equal footing in that regard, if anything WebLibre has an advantage since it's on No Restrictions and Chrome is on Battery Saver mode

[FaFre]

We need more logs since this seems device specific. Please install https://f-droid.org/en/packages/com.dp.logcatapp/ then prepare your test scenario. Set the app filter to #397 but without explicitly setting error/warning tags, we need everything. Then start capturing until the issue happens. If you don't wanna post the logs here, please send it over matrix.

[CHEYCKIT]

We need more logs since this seems device specific. Please install https://f-droid.org/en/packages/com.dp.logcatapp/ then prepare your test scenario. Set the app filter to #397 but without explicitly setting error/warning tags, we need everything. Then start capturing until the issue happens. If you don't wanna post the logs here, please send it over matrix.

Done, here you go

logcat_recording_2026-07-02_12-04-21.txt

[FaFre]

Mhm could you please try to reproduce it on a fresh profile/user without any changed settings? just finish the onboarding with quick and then try to reproduce it.

[CHEYCKIT]

Mhm could you please try to reproduce it on a fresh profile/user without any changed settings? just finish the onboarding with quick and then try to reproduce it.

Correct, I was not able to replicate the issue on a fresh profile, still problematic because most mobile users run hundreds of tabs in their browser of choice at all times

logcat_recording_2026-07-02_13-06-47.txt