Firefox

20721 readers

10 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago

MODERATORS

[email protected]

PWAs with Lemmy 0.18 instances very crashy on Android/Fenix fork (lemmy.world)

submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

Inb4 I know I have an old phone with low storage and old Android 9 and a slightly outdated Fenix fork (IceRaven/Fenix 112) with a bunch of extensions and the problem could be in any of these. Just wanna know if it's definitely on my end or maybe not. Because I never have this kind of problems with any other web site.

Anyway. I tend to use permanent Private mode apart from a couple PWAs, including some Lemmy instances. My "home" lemmy.world with 0.17.4 works well enough.

But I just realized that when using instances on 0.18 like lemmy.ml or lemmynsfw, minimizing the PWA (going to phone home screen) crashes the entire browser, including any other windows.

So, is it just me?

For comparison, I tried it on Bromite (yes I know it's not developed anymore): using the add home shortcut for 0.17.4 lemmy.world just indeed adds a browser shortcut. With 0.18 instances, the shortcuts make Bromite act like proper PWAs without the address bar etc. But not crashing.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 2 years ago (1 children)

Using Android 13 with Mull (Firefox fork) connected to my home instance on 0.18.0 and the PWA seems to be working as expected. Did have one crash notification yesterday I believe, but the PWA seems to be unloading from ram just about every time I switched apps anyway; which is very common on my phone.

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (1 children)

but the PWA seems to be unloading from ram just about every time I switched apps anyway

Well isn't that the problem? E.g. if I'm writing a comment and switch to another app, it disappears completely?

I also thought the pwa just "disappears", but as I was trying it a bunch of times, I got a "IcaRaven keeps crashing", so it's actually a crash then.

Also it closes all the other browser windows I have opened at the time. Of it's doing the same for you, that's a sign of a crash.

[–] [email protected] 1 points 2 years ago (1 children)

Well isn’t that the problem?

It's a problem with my OS since it does it with just about every app I use. Blame Oneplus and their shitty ram management.

[–] [email protected] 0 points 2 years ago (1 children)

So does it happen with regular Mull when you have a regular web page opened?

Btw I don't know if it changes anything, but IceRaven has a feature to auto-unload pages from RAM so that the OS doesn't need to kill it when minimized. While my phone is already not aggressive about closing apps, IR can easily stay in the background the whole night while some other apps get closed. Maybe give it a try.

[–] [email protected] 1 points 2 years ago

I'm pretty certain Mull does the same. Pages that haven't been exited but have sat unused are unloaded from ram, but on my phone the latest page will still get killed frequently. The issue is so prevalent that it's widely complained about example. Oneplus has a history of aggressively killing background apps.