message view spawning multiple processes that does not quit
Reported by moiraine | September 8th, 2020 @ 08:26 PM
On build 1.13.2 (5719), using the new message view, after viewing a couple of messages, mailmate will spawn multiple webview processes that does not quit (e.g. seen by searching for mailmate in the activity monitor, screenshot below); in terminal, the corresponding pid for the "about:" processes in the attached screenshot is
2541 ?? 0:00.34 /System/Library/Frameworks/WebKit.framework/Versions/A/XPCServices/com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent
Also, running on macos big sur beta (20A5374i), not sure if this applies to non-beta systems.
Comments and changes to this ticket
-
Florian September 27th, 2020 @ 06:25 AM
I can confirm the existence of many 'about:' processes, also on macOS Catalina 10.15.7 using MailMate 5721. For me it's >100 of those processes, each of which using 80-100MB of memory.
-
benny September 27th, 2020 @ 07:25 AM
- State changed from new to reproduced
I'm aware of this issue. It's actually a side-effect of an intentional feature (a cache of recently displayed messages), but the memory usage is naturally unacceptable. I'll have to figure out a different approach.
-
Florian November 16th, 2020 @ 08:15 PM
Besides the 'about:' processes mentioned above, I've also noticed multiple
MTLCompilerService
processes that are also related to MailMate. They're putting some real CPU load on my system and I usually need to close MailMate then, to be able to use my Mac normally again.In contrast to the 'about:' processes, they don't appear with every message read, but more seldomly — it seems related to HTML mails with images, but I'm not 100% sure.
-
Andrew Berry November 8th, 2021 @ 01:40 PM
This seems to have gotten worse either in the beta releases or with macOS 12. Even with 64GB of memory, this eventually causes system stability issues after a day or two. MailMate had around 1800 processes using 17GB of memory, and surprisingly it was affecting Safari as well.
Are there any workarounds for this?
-
benny November 14th, 2021 @ 10:26 AM
- State changed from reproduced to fixcommitted
Which revision are you using now? Hold down the command key when clicking “Check Now” in the Software Update preferences window. As far as I know, this should be much better now.
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.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Mac OS X email client.