High CPU (ß 5757)
-
Giovanni Lanzani
To maybe add some extra bit of info: Window Server also seems to spike together with MM
-
benny
You can help me by generating samples. When CPU is high, run the following Terminal command:
sample MailMate 10 > ~/mailmate_sample.txtThen send me the file(s) using “Help > Send Feedback” and reference this ticket.
-
Giovanni Lanzani
Since the latest beta, I cannot reproduce this behavior anymore. We can close it maybe?
-
benny
- State changed from new to cantreproduce
Thanks for letting me know. I'm a bit unsure if I actually did anything which could explain why this no longer happens. Let me know if the issue returns.
(Sorry about the spammer adding to the ticket.)
-
Oleg
- State changed from cantreproduce to new
Hi. I'm seeing the same issue with CPU usage now. Occasionally MailMate would start using 60-70% when seemingly idle (at least nothing is happening in the UI – I even switched to an empty account to remove any rendering woes). If I restart MailMate at this point, the issue goes away and MailMate backs down to <10% CPU.
I captured a sample as advised above - here it is attached to this message.
-
Tom Dietel
Hi. I have the same problem, with Mailmate using about 60% CPU and the WindowServer another 80% on a recent MacBook Pro. I also generated the samples file. However, it seems I cannot upload, because the quota has been reached.
-
benny
Please try again with the latest test release: Hold down the option key when clicking “Check Now” in the Software Update preferences pane.
(There's unfortunately almost never enough quota in the ticket system. Use “Help > Send Feedback” to send me files via MailMate.)
-
Oleg
Hi. I'm still seeing the same issue with the latest build 5875. I sent a fresh sample via email feedback from Mailmate.
Cheers
-
Tom Dietel
Hi.
I still occasionally had this issue with 5852. I have sent you an email with the sample as advised. I also installed the latest test build 5878 to see if the issue is still there.
Cheers, Tom.
-
benny
The theory is that this only happens on Big Sur (for some users). I have no reports on Monterey.
(I would be interested in knowing if anyone has this issue on Monterey with the latest test release.)
-
benny
- State changed from new to closed
I'll close this ticket, but I'm still interested if anyone has more details to add about when this might or might not happen.
-
Oleg
as a data point – I upgraded to Monterey about a week ago, and haven't noticed any CPU abuse since the upgrade
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
