VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed

gpatel-fr

@pparent said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:

importing a picture with contentHub directly from camera app to Whatsweb (probably works with another app than whatsweb), does reduce progressively the amount of available swap, when done several times,

I tried to repro on my FP5 without success, but of course there are many differences: other phone, more Ram (I have 8 Gb hence a swap of 4Gb) , I don't use Whatsapp or Signal so all the apps available to share in contentHub are files and messages. After a dozen of shared photos, zero swap, available memory in top goes down by one or two hundred of megabytes, then back up.

kristatos

Have you tried to lower the swappiness of the system? Maybe this could help to slow down the use of the swap-partition. On my phones (and Laptops) i set the swappiness to 10:

sudo sysctl vm.swappiness=10

If that works for you, you can make this permanent via a config-file

pparent

@gpatel-fr said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:

I tried to repro on my FP5 without success, but of course there are many differences: other phone, more Ram (I have 8 Gb hence a swap of 4Gb) , I don't use Whatsapp or Signal so all the apps available to share in contentHub are files and messages. After a dozen of shared photos, zero swap, available memory in top goes down by one or two hundred of megabytes, then back up.

Thank's a lot but I not sure to see how you can do it with files apps (or maybe there are import features that I don't know about, but I really don't see where).

Just to make sure I was clear with messages it would be:

1-Open messages app
2-Go to a conversation and click the attachment icon, then image
3-In contentHUb select camera
4-Take your picture and validate

I will to some more tests tonight including swapiness.

pparent

@kristatos said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:

sudo sysctl vm.swappiness=10

It does not seem to have clear impact on swap loss when importing from camera. I will see if the crash still happens in normal use, with this option in the coming days.

gpatel-fr

@pparent

thanks for the explanation, it's indeed faster than the more convoluted process I was following. So I did about 6 messages each having 5 photos, lomiri-messaging memory footprint increased steadily by about 100 K for each message (that I never actually sent, it was a dummy number). When I closed lomiri-messaging all this memory was reclaimed by the system, and if I open it again I don't get back the high memory use even if I open the same contact.

So there may be a leak but it hardly seems a blocker on my phone - that is, my current use of the phone is that as soon as I have finished using an app, I close it, and each evening I shutdown the phone for the night. You may use your device very differently of course.

kristatos

I've upgraded my Volla (yggdrasil) yesterday from 20.04 OTA-11 to 24.04-1.1 stable. Since then I already had two times where the phone freezes/crashes. When I press the power button to wake up the phone it seems that only the backlight is on but there is no picture. If pressing power button again, the backlight is off again. I can repeat this procedure several times without luck. Several minutes later the phone again wakes up like expected while pressing the power button.
After having a working phone again I checked the RAM&SWAP. Both of them were not totally used and had some reserve. Then today I tried to flood RAM&SWAP by starting many different apps and after a while my SWAP was filled 100% while the RAM does still have some free space. The phone is still usable and is not freezing/crashing...

pparent

@gpatel-fr said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:

So there may be a leak but it hardly seems a blocker on my phone - that is, my current use of the phone is that as soon as I have finished using an app, I close it, and each evening I shutdown the phone for the night. You may use your device very differently of course.

Yes I use to keep whatsweb always open to get notifications, and I rarely reboot the phone if it does not crash, except if I somehow run out of battery which happens rarely given the very good battery life of the phone

Those days I've not experimented any crash. I'm not sure why. The difference might be that during the Christmas celebration, I've shared and received and taken many pictures with messaging apps. But it might be something else. Because the leak that we have noticed seems to require too many imports to explain completely the problem.

@kristatos said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:

I've upgraded my Volla (yggdrasil) yesterday from 20.04 OTA-11 to 24.04-1.1 stable. Since then I already had two times where the phone freezes/crashes.

Well thank you for reporting, maybe you can add your experience to the bug report, so that it is clear the bug is not specific to my phone:

https://gitlab.com/ubports/porting/reference-device-ports/android11/volla-phone-22/volla-mimameid/-/issues/24

kristatos

@pparent Sure, I can complement your bug report. But do you have the same experience?

Press power button
Backlight powers up
No image is coming up

pparent

@kristatos said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:

@pparent Sure, I can complement your bug report. But do you have the same experience?

Press power button

Backlight powers up

No image is coming up

Yes I've seen it a few times as you describe, but most of the times I had a freeze with still image while using the phone and using the interface. In that later case the phone stays still in the last image, and pressing the power button does not have any effect. So I guess what you describe can be the same bug except that it happens while the phone is suspended, so when you press the power button it remains frozen on a black screen.

gpatel-fr

@pparent

going back to this problem, do you still see it ?

In a previous post, I said:

I have found a 'rogue' app that can reliably hang my phone.

for the record, it is the command line tool nix-index installed via crackle. I have absolutely no interest,in this command now, it was just an experiment that turned into a total phone hang, but I was intrigued by this UT killer.

So I started on a quest to install and configure systemd-oomd (yes, that's the system that made Canonical's reputation a bit worse). It was a bit difficult since I did not want to use apt, so it was all a game of building overlays mount and setting the configuration by hand.
It was not pretty but now it seems to be mostly operational.

I'm a bit pleased to see my first experiment come to a success. My UT killer was eliminated ruthlessly by systemd-oomd. If I start the accursed command via ssh, the ssh session used is killed, letting the other ssh sessions running. It I start it via terminal, the terminal is killed.

I'm going to use the phone a bit with this config to check that the system is stable with this addition. After that, if you want to test it, I could help you in this adventure, it could be interesting. If this is really useful, it that could be an interesting addition to UT for the next 26.04 iteration. Smooth the rough edges ! fix some of the crashes...