Closed ruscon closed 3 weeks ago
@ruscon hmm, that's strange.
By "turn it off" you mean "Force Quit" from "Activity Monitor"?
Would be nice to check it's CPU/RAM usage during that "slow down" phase to determine if it's CommandShift to blame =)
@VasylBaran no, just quit without force (from menu)
Would be nice to check it's CPU/RAM usage during that "slow down" phase to determine if it's CommandShift to blame =)
I understand, but it's hard to open anything when the MacBook hardly responds to your actions
@VasylBaran no, just quit without force (from menu)
Would be nice to check it's CPU/RAM usage during that "slow down" phase to determine if it's CommandShift to blame =)
I understand, but it's hard to open anything when the MacBook hardly responds to your actions
wow, it's that bad? Are you using M1/2/3 (Arm-based Mac) or an Intel-based one? Also how much RAM do you have?
If you face this issue again, please check RAM/CPU usage of CommandShift (from Activity Monitor) before pressing 'Quit' and post it here. It would be really helpful
Intel 2019y 64 gb ram, but with docker, etc(50 gb is busy)
Ok
@VasylBaran Hey. Today I came across the same problem again.
I don’t see any problems in the screenshots, maybe you will.
As usual, turning the program off and on again helped get rid of the problem.
2 weeks after, again
@ruscon please check the latest release, this issue should be fixed now. It would be great if you can confirm this. https://github.com/VasylBaran/CommandShift/releases/tag/1.03
I have noticed several times that my Macbook sometimes starts to slow down. And if I turn off “CommandShift”, the speed is restored.
Unfortunately, I don't have any evidence at the moment.