Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU usage on MacOS after long sleep/hibernate time #126

Open
DoDoENT opened this issue Aug 25, 2023 · 2 comments
Open

High CPU usage on MacOS after long sleep/hibernate time #126

DoDoENT opened this issue Aug 25, 2023 · 2 comments

Comments

@DoDoENT
Copy link

DoDoENT commented Aug 25, 2023

If I put my Mac to sleep and keep it asleep for a more extended period (more than 3 days), after waking the CPU is at 100% (all cores), and killing tmux helps. The process that takes the most CPU is ps (not an individual, but scores of ps processes).

My guess is that when Mac is asleep for a more extended period, many "save session" tasks are queued and all processed after waking up. The same pattern of CPU usage I have when manually issuing the session save command.

Is it possible to either:

  • disable auto-saving of session every 15 minutes, and let only saving be done manually?
  • or prevent queuing of "save session" tasks while Mac is asleep?

Of course, this is just my guess - maybe the origin of the problem is somewhere else. I'll be happy if someone else could reproduce this issue (I haven't been able on my Linux machine - it appears to be Mac-specific).

@BradLewis
Copy link

Did you ever resolve this issue? I am currently encountering it every morning after my mac is asleep over the night.

@DoDoENT
Copy link
Author

DoDoENT commented Jun 11, 2024

I worked around it by disabling auto-saving of my sessions and simply got into the habit of saving them manually every time when I introduce a significant change to my active sessions/windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants