Lately, I've noticed both the Morph & Sapot web browsers keep quitting.
-
@opolork I read in a post that QtWebEngine has been updated in dev channel. Maybe you can test.
-
@opolork What options are you referring to?
-
@opolork
Did you change lomiri scaling in UTTT ? -
I had the same with my fp2 and before that with my bq e5. Morph is not usable anymore in this devices as it crashes too often. I don t really understand why but maybe it just because the devixes are getting old and lack of ram? I m now using a fp3+ and there is no comparison as this device is new and powerful. But if there is a solution it would be great to give an other chance to my old devices
-
@opolork, you can try switching off and on, it is not the same as rebooting.
-
@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.
-
We now have the last update of Ubuntu Info (Walking-Octopus) with task manager to see the RAM consumption.
A usefull tool, thanks to Walking-Octopus. -
@mrt10001 said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
@opolork Have you rebooted the device and then cleared the browser cache? Have you removed and reinstalled the browsers? Have you checked for updates?
Hi MrT10001. I did all of those bar clearing the browser cache - I see no option in either web browser for that. I didn't uninstall/reinstall Morph since it's no longer in the Open Store.
-
@domubpkm Hi. I don't run the dev channel.
-
@kugiigi said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
@opolork What options are you referring to?
Hi. The settings in the web browsers.
-
@keneda said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
@opolork
Did you change lomiri scaling in UTTT ?Hi. No. Should I?
-
@redxxiii said in Lately, I've noticed both the Morph & Sapot web browsers keep quitting.:
Morph is not usable anymore
Hi. I agree.
-
@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?
-
@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
-
@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