search

GrapheneOS / os-issue-tracker

Issue tracker for GrapheneOS Android Open Source Project hardening work. Standalone projects like Auditor, AttestationServer and hardened_malloc have their own dedicated trackers.
https://grapheneos.org/
348 stars 19 forks source link

Lots of crashes after update to 2024070900 bluejay. #3750

Open schichtnudelauflauf opened 1 month ago

schichtnudelauflauf commented 1 month ago

Stable channel on bluejay. Official Build 2024070900

After the update that lead to above buildno., when the post update app optimization started, many of the iterations were stuck, retried (the counter thrashing back&forth) and generated dex2oat crash notifications.

Then multiple system processes crashed and it did a soft reboot (-> Graphene logo -> Pre-decrypt lockscreen). Since then It takes at most a bunch of seconds before soft rebooting again after unlocking.

I will try to get the logs out. I had a glimpse. It was a bunch of aborting errors from hardened_malloc and processes ending with segfault.

Testing Safe Mode

Lots of crash notifications. System still up after a minute. Optimization proceeding.

Crashed process names:

After about 10 min even Safe Mode had system crashes and soft reboot. App Optimization starting yet again.

New crashed process names:

The counter of apps to be optimized has gotten smaller between reboots. So its not really stuck. Lets see if one does not get through.

UPDATE App optimizer went through in Safe Mode, no further process crashes. Left it on, after some minutes it was just off. On restart to normal boot I got a kernel crash notification.

I am aware of:

Also congrats to you people for doing the yet most stable android update channel I have ever seen. I think this OS had stable updates with problems only twice since its called Graphene as far as I can remember.

Logs:

android.hardware.audio.service crash 0e66a58355bb.txt com.android.settings crash 5f81bde54821.txt com.android.systemui crash 1a32e880a683.txt dex2oat64 crash 2a9ee1b01288.txt dex2oat64 crash 6deb87891a4a.txt dex2oat64 crash 9b24264df573.txt dex2oat64 crash 376da4bd5f1f.txt dex2oat64 crash a47b09ec8067.txt dex2oat64 crash a47bac588bfb.txt dex2oat64 crash df36d9bdd763.txt dex2oat64 crash e777aaba4b41.txt surfaceflinger crash a27cf41cfc91.txt system_server crash c7018d461189.txt system_server crash f1d996957896.txt Kernel crash b0e4a945836f.txt

schichtnudelauflauf commented 1 month ago

The kernel crash Kernel crash b0e4a945836f.txt

schichtnudelauflauf commented 1 month ago

😢

Would a rollback or n-patch-revert fix that and at what cost?

If I turn on my primary phone and it updates, I'll have 2 currently unusable devices.

Do you have a link for context?

thestinger commented 1 month ago

There's no known issue with the latest release and there were not changes which could have caused this. It seems your hardware is failing.

schichtnudelauflauf commented 1 month ago

Hm. I'll update if this stops happening or other peculiar things happen anyways. Maybe there actually is something generally interesting coming from this.

That would have been quite the short phone life without major accidents.

schichtnudelauflauf commented 1 month ago

It just stopped happening. The only change inbetween was another update. 2024071200 I have no info if the update is related. It seems either the crashing or safemode also reset some settings that I didn't expect it to reset in normal boot. Some I am quite grumpy about being unexpectedly reset.

Could this be an intrusion? Kinda hard to prove or disprove because dumping things is hard in a production build.