A note for support and developers at eM: The bug in Apple MacOS 15 does not cause a crash in the two other email clients I use. I can’t say anything about the current version of the eM client because I only use it to search for old emails whose conversion to the other two should be faulty (mostly PDF attachments).
The fact that you don’t experience crashes in two other email clients does not mean that Apple is not responsible for the bug/crash. That’s not how it works. Other clients may use different system components or configurations so they are not affected by this bug. This is quite a specific bug in webkit, the component used for email viewing. The bug is confirmed by Apple, marked as security risk, but still not fixed. It is happening in other software like Eclipse too and fix or workaround is not yet known. As I’ve already mentioned meanwhile we are trying to find a workaround for the problem by ourselves, but it is a tedious job and basically a black box for us. You can check the status of this Apple bug by yourself. We’ve posted a link to the issue here in forum.
Yes it is quite hard to be dependent on a code of big guys, but it is even harder that you are always blamed for their errors. With this one the situation is pretty clear.
1 Like
Has anyone who receives the macOS beta updates seen if this fix might be included already but not released. I am so OCD that I would even risk joining the beta program just to stop this eM Client crashing every time I open a window in the program to read an email.
I apologise that my comment was misunderstood.
I did not mean to criticise eM by referring to two other email clients, but to convey the hope for others that there might be solutions from eM.
Once again, I apologise.
That’s quite interesting to hear. It may mean that this won’t be a macOS update or a Safari update, it may be pushed out by Apple as a security patch. Apple seem to be aware so hopefully they’ll roll out an update soon! 
Update: I installed the macOS 15.5 beta (24F5053j) and it did NOT change the frequency of crashes. So no
No we know it is not fixed in 15.5 beta 3, hopefully in beta 4, there are some rumors that beta 4 might fix it, but we can’t be sure yet.
I have the same problem: constant crashes. I don’t get a message about any certificates, the programme just disappears from the screen. This has been the case for some time now. Is there any hope that the problem will be resolved in the foreseeable future?
Michal has just posted an updated version which may solve the problem for now. For those who are interested in trying it and seeing if it helps, more information is here:
Fingers crossed!
1 Like
Seems like version 10.3.1720 fixed the problem. Since yesterday eM Client still running without any crash.
2 Likes
Run Vers. 10.1.4828 on MacBook Air M3. This Version frequently crashed. Often noticeable with faster actions using the mouse.
I am not sure I understand the statement. Have you installed the new (10.3.1720) version and it stopped happening?
Just downloaded the update released today 10.3.1720 and no crashes. Thank you!
1 Like
Mine was and is still crashing with version 10.3.1720 and also with the beta you sent me today (10.3.1738_Mac).
To be frank, I am running some debug analyzers and it looks to me, it’s something to do with your db sync mechanism. I don’t understand why the database is always corrupted on crash. Your architecture should be able to revert any db changes after a crash to the state it had been prior any db change has been committed.
I was happily using Postbox (which you acquired recently some months ago!) for many years. I thought I should migrate to your eM Client as Postbox is expected to no longer be maintained. However, I will continue using Postbox until I have identified a more stable alternative. No one has time to sustain your constant product crashes, db rebuilds and data sanitation activities.
I will continue using Postbox until I have identified a more stable alternative.
Have you tried a brand new database without importing any exiting postbox data ?
If you haven’t, close eM Client and then go to the following eM Client hidden data folder and rename it to eg: eM Client-old . Then reopen eM Client and setup as new. Then see if it still crashes.
(Mac Hidden hidden eM Client database folder)
“Users\yourusername\Library\Application Support\eM Client”
1 Like
I’m sorry to hear you’re still having troubles. v10.3.1720 solved the crashing issue for me and I’ve not had a single crash since then. When the frequent crashes did happen with an earlier version of v10.3, I was glad that eM Client checked for any corruption at the start (not all clients do that, and I’ve experienced mailbox corruption in Postbox) and usually it was fine, although once or twice it did repair something. This is not to play down your experiences, only to say these differences might actually help with diagnosing where this is coming from.
I was going to suggest a similar approach to what cyberzork wrote. It’s worth trying a fresh install of eM Client without importing anything from Postbox or anywhere else. If that sorts the problem and then later re-importing Postbox or other data causes the crashing to return, that would help to track down the cause.
In Settings → Advanced → Logging, you can configure logging with a number of aspects of the software. These might help the Support team with diagnosing the issues if you end up contacting them.
I hope you manage to get to the bottom of it.
1 Like
Is there any news on this? Is the crashing on Mac solved for everyone?
I moved from Windows to MacOS this week with a new Macbook and fresh installation of all software. Currently on MacOS Version 15.6 (24G84) and eM Client 10.3.2622 (9cd48bf) and in the few days I have been using eM Client it has crashed on my repeatedly already. This morning twice. The last time was while deleting a mail from the inbox.
Everything is fresh, did not move any mailbox but did a fresh install and manual added all mail accounts.
Sorry to hear that, MaSansky. I’m using the same versions of macOS and eM Client as you, but I’ve not experienced crashing like that for some time (probably since April).
I’ve had a very occasional hang, perhaps every couple of weeks or longer, but many of them sort themselves out and don’t need me to Force Quit.