mirror of
https://github.com/AppHouseKitchen/AlDente-Battery_Care_and_Monitoring.git
synced 2026-03-24 18:31:47 +01:00
High CPU load #230
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wazar on GitHub (Aug 14, 2021).
Using Pro (1.06)
Macbook Pro (M1, 2020)
Latest macOS Big Sur
AlDente uses 99.99% CPU in activity monitor and sometimes hangs using 800% (logs attached)

aldentepro-debug-2021-08-13-18:27:42.pasta.zip
Quitting the app immediately drops CPU temp and load.
@JongYun-Kim commented on GitHub (Aug 15, 2021):
I've got the same issue...
100% cpu used.
750-800% cpu is used when I adjust the charge limit...
This makes my MacBook so hot. It's never been this hot before...
I uninstall the free version and installed this pro version through SetApp.
M1 MBA (11.4 and 11.5.2)
It may be worth noting that SetApp provides AlDente pro ver. 1.06, which I don't recognize in this repository...
@Rag0n commented on GitHub (Aug 16, 2021):
Same issue, I'm using AlDente Pro from Setapp and I have MacBook Pro m1.
@itz-Jana commented on GitHub (Aug 16, 2021):
Same, MBA M1 through Setapp.
@JongYun-Kim commented on GitHub (Aug 16, 2021):
I heard from AppHouseKitchen that they are working on it. They can't reproduce the bug at the moment though..
And, They added that "The one on SetApp is actually the newest version, which we have not released on GitHub yet. However, we will do so soon."
@davidwernhart commented on GitHub (Aug 18, 2021):
Hi Guys!
We are aware of this bug and have finally been able to replicate it.
A fix will be released soon!
Thank you for your patience,
David
AppHouseKitchen
@JongYun-Kim commented on GitHub (Aug 18, 2021):
Thank you very much.
Now that I hear that the new version is released soon, I can't be happier!
@davidwernhart commented on GitHub (Aug 19, 2021):
We have just released our new Version 1.07 which fixes this bug. Sorry for the inconveniences and kind regards, David