Lately, I've noticed both the Morph & Sapot web browsers keep quitting.
-
@redxxiii said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
I m now using a fp3+ and there is no comparison as this device is new and powerful.
Does the torch work? Anything not working properly in the FP3?
How can you trust that an app really won't send some company your location data, when you tell it not to? The only way you can trust a program not to do something it isn't supposed to do is if it is free software. ~ RMS
-
@bolly said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
@opolork, you can try switching off and on, it is not the same as rebooting.
Done. No change.
-
@kugiigi said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
@redxxiii Sadly, RAM is indeed a factor. Webviews seem to take a lot of memory though ideally the browser/app itself shouldn't close. Morph and Sapot tries to unload tabs but sometimes it's not enough.
Web browsing is painfully slow.
-
@opolork i did a wipe installation with my fp2 but nothing changed... That is why I think it is related to the hardware being old. But I can t prove that
Fairphone 3+ / BQ Aquaris M10 FHD / BQ Aquaris E5
-
@opolork the torch works! That is amazing after years using the fp2
anything that do not work properly with the fp2 is working well with the fp3. And the battery is amazing! But you will have some bugs. GPS can take some time to locate you. Pure maps use to freeze so you may have to reboot the app several times before routing. Display can be laggy sometimes but not a big deal. The worst bug is the lic not being useable by the apps after a phone call. You need to reboot the phone prior to take a video. But there is a workaround with a smart script that works well. I need to try it. That s all I can think now ! -
Morph also crashing on pixel 3a as of today. A lot of webapps (Gmail for example) crash as well so it has to be related to qtwebengine. I m writing this on Waydroid browser... will reboot and report
-
@emphrath Are you on devel?
-
@opolork
No.
Just there are issues causing morph crashing with some scalings in certain situations.
See here and also 311 and 312 :
https://gitlab.com/ubports/development/core/morph-browser/-/issues/310I had this 310 issue on settings crashing morph on OTA 11, gone on OTA 12, but i don't know how this was sorted, maybe a comeback lol.
Still having 311 an 312, so i reverted back my scaling.
Edit : there are also other grid values that can crash morph https://gitlab.com/ubports/development/core/morph-browser/-/issues/535
-
@kugiigi nope, rc. Anyway a reboot fixed it, so I guess it's some sort of memory leak
-
@keneda Those crashes were related to UITK's dialogs/popups. Morph has weird issues and crashes. I wanna try to replace all UITK components in Sapot and see if it reduces or even eliminates these.
-
@kugiigi
Not the 310 one i believe, as entering settings in morph, doesn't involve popup i guess. -
@keneda Oh interesting, I didn't know that has been a known issue. Never encountered it myself, only for the dialogs like Downloads and Bookmarks.
-
@redxxiii said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
@opolork i did a wipe installation with my fp2 but nothing changed... That is why I think it is related to the hardware being old. But I can t prove that
I think you kinda already proved it.
