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/
361 stars 21 forks source link

SystemUI stops responding for a long period of time #531

Closed thestinger closed 3 years ago

thestinger commented 3 years ago

This issue is intended to track generic issues tied to the SystemUI component not responding for a long period of time. It's likely that this is an upstream bug uncovered by hardened_malloc or a similar hardening features. Some users are reporting this problem but most people are not encountering it and I'm not able to reproduce it myself.

Please do not post in this thread without providing a bug report zip in an email to contact@grapheneos.org unless you're a developer working on the issue or come up with a reliable way of reproducing the problem. It's not helpful to post that you're experiencing the issue without providing that information and clutters the thread.

thestinger commented 3 years ago

Our current suspicious is that there's an upstream bug in the ANR (App Not Responding) handling. GrapheneOS hardening features sometimes uncover bugs in apps and may increase the frequency of them triggering ANR. If there's an upstream problem with this, it would be encountered more often on GrapheneOS. It's also possible that there are issues triggered during the process of creating the debugging data from encountering the issue. So, it's likely that this is a combination of various upstream issues that are uncovered or aggravated by GrapheneOS hardening features.

renlord commented 3 years ago

This does not seem to be an issue anymore. The OOM killer is alot more aggressive now with killing other user applications while keeping SystemUI fluid and running.

Still somewhat annoying (i.e. it kills a Whatsapp/Signal Video Call while you're having an engaging conversation).

modernNeo commented 3 years ago

@renlord Is this really still not an issue? What is happening on my end is when firefox app experiencing an issue, it caused the whole OS to crash. While Firefox itself should not be crashing, should an App crash be capable of causing the whole OS to crash?

renlord commented 3 years ago

@renlord Is this really still not an issue? What is happening on my end is when firefox app experiencing an issue, it caused the whole OS to crash. While Firefox itself should not be crashing, should an App crash be capable of causing the whole OS to crash?

What do you mean by crash?

If applications are being terminated, it is OOMkiller doing its job.

modernNeo commented 3 years ago

What do you mean by crash?

I mean, when this happens on my pixel 4, it can range from the UI just stops responding for a few minutes to the entire OS crashing and I have to boot my phone up again. I was in email communication with @thestinger and shared my logs with them and they indicated to me that the problem was some sort of firefox bug.

If applications are being terminated, it is OOMkiller doing its job.

It's not always the app being terminiated, the issue is the OS itself crashes as a result of the bug.

thestinger commented 3 years ago

Should be resolved in 12.

modernNeo commented 3 years ago

@thestinger can this be resolved when 12 is actually released?

thestinger commented 3 years ago

Issues are closed when they're resolved in the development branch as with nearly every other software project.