You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
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 ofps
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:
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).
The text was updated successfully, but these errors were encountered: