10.3 stability

I was testing 10.3 on an M2 MacBook Air last night and encountered a couple of crashes, which were not reproducible (see other thread: 10.2 Beta on macOS seems unstable). That makes it difficult to narrow down the cause.

Overnight, I installed 10.3 on my main machine too (an M1 MacBook Pro with 64 GB of RAM, running macOS 15.4) and left it importing folders from Postbox and downloading latest files from the Outlook server.

Using the M1 MBP today, I’ve had a couple of hangs when it was running but not in use by me, where I had to use Force Quit. Just now, I’ve had eM Client crash when I wasn’t doing anything. I sent the log to Apple and remember there was a SIGSEV issue, but don’t remember the finer details. (I’d copied and pasted before sending, and then foolishly copied something else afterwards too, so I lost the information. :roll_eyes: )

@Michal_Burger @Olivia_Rust Are there logs which would be useful to the eM Client team and, if so, which ones will be of interest and do I send them through the app itself (within the Preferences)?

It just happened again. This time, I can copy and paste the fault, which looked the same:

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Codes: 0x0000000000000001, 0x0000000000000018

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [51240]

My issues seems to happen when leaving eM Client open for a while and coming back to it maybe when the device hibernates. Just like the other day when I got to work and tried to open eM Client it was non-responsive so I looked at activty monitor and saw this:
eM Client 041025

Do you also have version 10.3?

Yes, I upgraded to 10.3 yesterday on both of my macOS devices hoping it would help.

Do you already have macOS 15.4?

Hi @Michal_Burger. I’m not sure which one of us you’re asking these questions, but I believe @kgiddings and I are both using macOS 15.4, if I understood his response to you in the other thread correctly.

It could be eM Client 10.3 or it could be macOS 15.4 that is the cause of the experienced instability.

With regards to my earlier question, are there any logs (or any other information) that would be useful for you? I’m happy to provide whatever I can to help.

I can confirm I am using macOS 15.4 on both devices as well as 10.3 eM Client on both. I’m installing build 10.3.1524 on my Macbook Pro now upgrading from the 10.3 build released yesterday. I installed it earlier on my Macbook Air and did not have issues after that. I did however come home and have to force quit the app prior to upgrading to 10.3.1524 due to the app being non-responsive. This time the memory usage seemed ok but CPU was high and never lowered. I waited a while before quitting the app to see if it would process what it needed to and idle back down but it did not.


.

Oh, interesting. How did you learn about the very rapid update?

I tried doing a check for updates within eM Client but it said there were no available updates. I’ve had a look on the web pages just now and see the update you mention, so I’m manually downloading and installing.

Did a member of the support team tell you about the release or was it by chance that you saw it?

I use an app called MacUpdater and it told me there was a new version so I went to check the release page and release notes. It seems the issue has something to do while leaving the app running but not in active use. I can’t recall 100% but I think my issues have been when getting on my device for the first time after being idle as while such as getting to work and using my air or getting home and using my pro. I remembered on my original v9 to v10 beta testing that the command “/Applications/eM Client.app/Contents/MacOS/eM Client” entered into terminal will generate output in terminal that may help them narrow down the issue so I am doing that now with the build released from today. Time will tell if the new build helps or not but hopefully if not I will have something in terminal that helps narrow down the issue.

1 Like

I can confirm this bug. emClient regularly crashes when it is in the background and I try to bring the app to the foreground. On macOS 15.4

Hi everyone,
If you experience crashes with the macOS version, please send us Terminal logs so we can look into this and resolve it asap.

Please run eM Client from Terminal (Cmd+Space) and type in
“/Applications/eM Client.app/Contents/MacOS/eM Client”
Hit enter and try to reproduce the problem.
A detailed log should appear in the Terminal after eM Client crashes again so just copy the log and then send it to [email protected], ideally with link to this forum post in the body.

Thank you for your cooperation!

1 Like

@kgiddings Ah, I see how that worked now, thanks. The quiet release of a new version without reference to the preceding one in the release notes makes me think they caught something and have implemented a rapid fix. That’s an interesting potential observation about when you noticed the problems might happen. Sometimes eM Client for me had simply crashed when I’d thought I’d not done anything, sometimes it was hanging while just running in the background, and there were a couple of times it crashed suddenly when I tried clicking on something. Very useful to know about the Terminal trick too, thanks.

@ago Sounds like it’s not just one or two of us, then. It’s worth downloading the update that quietly came out yesterday (10th April) and seeing if that fixes things.

@Olivia_Rust Thank you, I appreciate you getting back to us with offers to help and details of ways we can provide useful information for the developers.

I’ll also provide more information here about the systems I use and the experiences:

1) Office desktop
Mac Studio, M2 Ultra, 64 GB
macOS 15.3 (profile restricted updating to 15.4 yet)
eM Client 10.1 (v10.1.4828.0)
This was my installation for testing before on the more critical machine for daily use when travelling. This instance of eM Client has been working fine for a few weeks. I don’t remember it hanging or a crash.

2) Travel laptop
MacBook Air, M2, 8 GB
macOS 15.4
eM Client 10.1 and then 10.3 (v10.1.4828.0, then v10.3.1503, and now 10.3.1524)
I started with v10.1.4828.0 and it seemed fine. I updated to v10.3.1503 on the 9th April and immediately experienced the two (non-reproducible) crashes. On the night of 10th April, yesterday, I updated to 10.3.1524.0 and tested it briefly. No crashes yet, but too early to be sure.

3) Main machine
MacBook Pro, M1 Max, 64 GB
macOS 15.4
eM Client 10.3 (started with v10.3.1503 and now on 10.3.1524)
This was my main target for installing eM Client, doing so only when 10.2/10.3 would be out because it was the machine running Postbox; I had large amounts of E-Mail and attachments stored. I started with v10.3.1503 on the 9th April and the next day I encountered the app hanging a couple of times, needing me to intervene with Force Quit, and I’ve also experienced a couple of crashes. I fell back on to Outlook for most of the day because eM Client was feeling unstable. Yesterday night (10th April), I updated to 10.3.1524.0 and crossed my fingers. No hangs or crashes… I’ve tentatively switched back to eM Client today on this machine and will see how it goes. Dare I say it, it has been working much better. :crossed_fingers:

I’m on emClient 10.3,1503 and it’s the same as before.

Had a crash when I tried popping a message out in a separate window. I’ll run the Terminal command and see whether this was just a coincidence or whether issues remain.

When I call this up in the terminal, I get an error message. I’m out of here for now. I’m a freelancer and have a lot of work on my desk. Testing and beta testing is not one of my tasks. Get back to me with a bugfix. Thank you.

I’ve started the app again via the Terminal and it is doing its database checks. Will let you know how things go and send any logs generated. I noticed the command wouldn’t run and realized there were spaces in the command that was shown above. To correct this, I’ve run the following with the inclusion of back slashes in two places to get past the spaces:

/Applications/eM\ Client.app/Contents/MacOS/eM\ Client

1 Like

@eMDash It should work if you enclose the command string in " ".

2 Likes

I am using em Client 10.3 on a macbook pro running sequoia 15.4. Since updating to 10.3 my em Client crashes constantly - enough for me to have had to reinstall Outlook. I would much prefer using em Client but not if it has to restart every 30 minutes or so. I don’t have a pattern by the way - at first it happened when switching to calendar view but now it occurs when I am reading emails.

Hello @agileDogs and welcome to the forum. Are you running v10.3.1524.0 (10th April) or the preceding version, v10.3.1503, which was released the day before (9th April)? My experience so far has been there are still crashes with 10.3.1524.0 but it may be a little more stable than 10.3.1503.

The release history can be found at: Release History | eM Client