Repository navigation
Conversation
Author
|
bumping this @SimonSchubert this is causing huge cpu usage and battery drain 😄 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On my phone Omalauncher shows about 6 hours in the background and 2 hours of CPU with the screen on for a few minutes.
Now and then the Linux session gets killed and restarted while the app stays alive. A widget shell (
bash --noprofile --norc) from the old session is left behind with parent PID 1. It sits at about 100% CPU until I force-stop the app or reboot. It also has a defunctheadchild, which looks like the| head -cinGuestShell. I logged this for a few days: 15 to 40 times a day, and every leftover hadlibproot-loader.soas its executable.ProcessTree.ktalready says that when a proot is SIGKILLed, its processes keep running untraced and spin.Proot.killAll()cleans up exactly these, but it only runs when Linux is stopped or removed. Nothing calls it when the app starts, so leftovers from the previous run stay.This calls
proot.killAll()once at the start ofRuntime's init. The app has a single process and no proot exists yet at that point, so everything it finds is a leftover.I haven't built this or run it on a device, so none of the checklist below is ticked. I also don't know what kills the proot in the first place, only that the leftovers are never cleaned up afterwards.
./gradlew :owl:test :app:testFossDebugUnitTest :owl:owlJar :app:assembleFossDebug :app:lintFossDebugpasses