Mail just crashed

[gank41]

Check out my post here.

Mail Import Failed After Sonoma Upgrade

Hi everybody, After installing Sonoma on my 2018 Intel Mac mini, Apple's Mail App all of a sudden decided it wanted to "Import my Mail" in order to continue.. Ok, sure. That happens from time to time with different app databases needing to be updated and whatnot. Well, in my case, maybe yours, I...

forums.macrumors.com

 

[djcraze]

The only way to reset Mail to factory is the method I outlined, unfortunately. It really sucks that you're having these issues. I do think that your issue will be resolved if you reset everything mail related per my directions, though.

 

[kagharaht]

Check out my post here.

Mail Import Failed After Sonoma Upgrade

Hi everybody, After installing Sonoma on my 2018 Intel Mac mini, Apple's Mail App all of a sudden decided it wanted to "Import my Mail" in order to continue.. Ok, sure. That happens from time to time with different app databases needing to be updated and whatnot. Well, in my case, maybe yours, I...

forums.macrumors.com

Here is the weird part. I have no other accounts. Only one. iCloud mail account. @Mac.com. Also I have no email saved locally on the drive. It's all on iCloud. So there was nothing to import from any account or drive. I simply signed in to iCloud when setting up the new iMac. Even all my files are on iCloud. It's basically nothing imported from any drives or Mac. Everything came from iCloud server.

 

[kagharaht]

The only way to reset Mail to factory is the method I outlined, unfortunately. It really sucks that you're having these issues. I do think that your issue will be resolved if you reset everything mail related per my directions, though.

Yes I'm gonna do this. All my mailboxes in iCloud will not get deleted right? I hope? LOL... I'm gonna save them as mBox files on another external backup drive individually just to be safe. 🙂

 

[gank41]

Here is the weird part. I have no other accounts. Only one. iCloud mail account. @Mac.com. Also I have no email saved locally on the drive. It's all on iCloud. So there was nothing to import from any account or drive. I simply signed in to iCloud when setting up the new iMac. Even all my files are on iCloud. It's basically nothing imported from any drives or Mac. Everything came from iCloud server.

Everything in my example was for iCloud, and other "Server Based" email accounts. Nothing was local, but there's always preference files and things. The other poster noted the AppCleaner app. I use TrashMe3, but they both do the same. The goal is to remove the Preference Files from the Mail app, regardless of account type. I would still verify the folders are removed as explained in my post after using your app of choice to remove the Mail app Folders. Just to confirm.

 

[kagharaht]

The only way to reset Mail to factory is the method I outlined, unfortunately. It really sucks that you're having these issues. I do think that your issue will be resolved if you reset everything mail related per my directions, though.

Ok I just did it. Mail crashed again with similar error. So I hope this fixes it. Thank you!

Edit: The only thing I've enabled is "Junk Mail" filtering. I've left everything alone with Mail settings. I don't even have rules enabled. Just leaving it as is and see if stops unexpectedly quitting on me.

 

[kagharaht]

Crashed again. AppCleaner wasn't able to fix it.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: Mail [980]
Path: /System/Applications/Mail.app/Contents/MacOS/Mail
Identifier: com.apple.mail
Version: 16.0 (3774.500.171.1.1)
Build Info: Mail_App-3774500171001001~13
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-05-06 14:14:53.2983 -0700
OS Version: macOS 14.4.1 (23E224)
Report Version: 12
Anonymous UUID: 761C5C29-5BBD-078A-ABEB-86F07CA61331


Time Awake Since Boot: 140000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGKILL)
Exception Codes: UNKNOWN_0x105 at 0x00000000dac11a30
Exception Codes: 0x0000000000000105, 0x00000000dac11a30

Termination Reason: Namespace PAC_EXCEPTION, Code 261

VM Region Info: 0xdac11a30 is not in any region. Bytes before following region: 665413072
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 1026a8000-102ac0000 [ 4192K] r-x/r-x SM=COW /System/Applications/Mail.app/Contents/MacOS/Mail

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x1931ce000 object_getClass + 28
1 Foundation 0x194786d34 _NSKeyValueObservationInfoGetObservances + 252
2 Foundation 0x194ea2b10 NSKeyValueWillChangeWithPerThreadPendingNotifications + 236
3 AppKit 0x1971d81f4 -[NSWindow _screenChanged:] + 124
4 AppKit 0x1971d8158 -[NSWindow _displayChangedSoAdjustWindows:] + 112
5 AppKit 0x197c959a8 ___NSApplicationPerformScreenInvalidationReactions_block_invoke + 84
6 AppKit 0x196ecf8b0 -[NSApplication enumerateWindowsWithOptions:usingBlock:] + 236
7 AppKit 0x197c954c4 ___NSApplicationReactToScreenInvalidation_block_invoke + 856
8 AppKit 0x197c94e7c _NSApplicationReactToScreenInvalidation + 292
9 AppKit 0x197c95054 -[NSApplication(ScreenHandling) _reactToDisplayChanges:] + 372
10 AppKit 0x197659d9c _NSCGSDisplayConfigurationUpdateAndInvokeObservers + 416
11 AppKit 0x19765a508 _NSCGSDisplayConfigurationMaximumHDRValueChangedNotificationHandler + 264
12 SkyLight 0x198d603e8 (anonymous namespace)::notify_datagram_handler(unsigned int, CGSDatagramType, void*, unsigned long, void*) + 876
13 SkyLight 0x1990fe224 CGSDatagramReadStream::dispatchMainQueueDatagrams() + 228
14 SkyLight 0x1990fe120 invocation function for block in CGSDatagramReadStream::mainQueueWakeup() + 28
15 libdispatch.dylib 0x1933ec750 _dispatch_call_block_and_release + 32
16 libdispatch.dylib 0x1933ee3e8 _dispatch_client_callout + 20
17 libdispatch.dylib 0x1933fcbb8 _dispatch_main_queue_drain + 988
18 libdispatch.dylib 0x1933fc7cc _dispatch_main_queue_callback_4CF + 44
19 CoreFoundation 0x1936bf4ac __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
20 CoreFoundation 0x19367cc30 __CFRunLoopRun + 1996
21 CoreFoundation 0x19367be0c CFRunLoopRunSpecific + 608
22 HIToolbox 0x19de17000 RunCurrentEventLoopInMode + 292
23 HIToolbox 0x19de16e3c ReceiveNextEventCommon + 648
24 HIToolbox 0x19de16b94 _BlockUntilNextEventMatchingListInModeWithFilter + 76
25 AppKit 0x196ed4970 _DPSNextEvent + 660
26 AppKit 0x1976c6dec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700
27 AppKit 0x196ec7cb8 -[NSApplication run] + 476
28 AppKit 0x196e9ef54 NSApplicationMain + 880
29 dyld 0x1932160e0 start + 2360

Thread 1:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x19355e1f4 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x193570b24 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x193566e34 mach_msg_overwrite + 476
3 libsystem_kernel.dylib 0x19355e578 mach_msg + 24
4 CoreFoundation 0x19367e058 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x19367c91c __CFRunLoopRun + 1208
6 CoreFoundation 0x19367be0c CFRunLoopRunSpecific + 608
7 CFNetwork 0x198b15890 0x1988b5000 + 2492560
8 Foundation 0x1947a8520 __NSThread__start__ + 716
9 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
10 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 2:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x193569358 __select + 8
1 CoreFoundation 0x1936a730c __CFSocketManager + 640
2 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
3 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 3:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x19355e1f4 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x193570b24 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x193566e34 mach_msg_overwrite + 476
3 libsystem_kernel.dylib 0x19355e578 mach_msg + 24
4 CoreFoundation 0x19367e058 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x19367c91c __CFRunLoopRun + 1208
6 CoreFoundation 0x19367be0c CFRunLoopRunSpecific + 608
7 AppKit 0x196ffdcb4 _NSEventThread + 144
8 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
9 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 4:: com.apple.coreanimation.render-server
0 libsystem_kernel.dylib 0x19355e1f4 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x193570b24 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x193566e34 mach_msg_overwrite + 476
3 libsystem_kernel.dylib 0x19355e578 mach_msg + 24
4 QuartzCore 0x19b8af870 CA::Render::Server::server_thread(void*) + 556
5 QuartzCore 0x19b8af634 thread_fun(void*) + 32
6 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
7 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 5:: WebCore: Scrolling
0 libsystem_kernel.dylib 0x19355e1f4 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x193570b24 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x193566e34 mach_msg_overwrite + 476
3 libsystem_kernel.dylib 0x19355e578 mach_msg + 24
4 CoreFoundation 0x19367e058 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x19367c91c __CFRunLoopRun + 1208
6 CoreFoundation 0x19367be0c CFRunLoopRunSpecific + 608
7 CoreFoundation 0x1936f9e3c CFRunLoopRun + 64
8 JavaScriptCore 0x1afb289c4 WTF:😀etail::CallableWrapper<WTF::RunLoop::create(char const*, WTF::ThreadType, WTF:🧵:QOS)::$_1, void>::call() + 52
9 JavaScriptCore 0x1afb4be50 WTF:🧵:entryPoint(WTF:🧵:NewThreadContext*) + 244
10 JavaScriptCore 0x1af997764 WTF::wtfThreadEntryPoint(void*) + 16
11 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
12 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 6:: LocalStorage
0 libsystem_kernel.dylib 0x1935619ec __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x19359f55c _pthread_cond_wait + 1228
2 JavaScriptCore 0x1afb4ebf0 WTF::ThreadCondition::timedWait(WTF::Mutex&, WTF::WallTime) + 160
3 JavaScriptCore 0x1afb21154 WTF:😛arkingLot:😛arkConditionallyImpl(void const*, WTF::ScopedLambda<bool ()> const&, WTF::ScopedLambda<void ()> const&, WTF::TimeWithDynamicClockType const&) + 2072
4 WebKitLegacy 0x1ad43659c WebCore::StorageThread::threadEntryPoint() + 440
5 JavaScriptCore 0x1afb4be50 WTF:🧵:entryPoint(WTF:🧵:NewThreadContext*) + 244
6 JavaScriptCore 0x1af997764 WTF::wtfThreadEntryPoint(void*) + 16
7 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
8 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 7:: CVDisplayLink
0 libsystem_kernel.dylib 0x1935619ec __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x19359f55c _pthread_cond_wait + 1228
2 CoreVideo 0x19c078094 CVDisplayLink::runIOThread() + 732
3 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
4 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 8:: com.apple.CFNetwork.CustomProtocols
0 libsystem_kernel.dylib 0x19355e1f4 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x193570b24 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x193566e34 mach_msg_overwrite + 476
3 libsystem_kernel.dylib 0x19355e578 mach_msg + 24
4 CoreFoundation 0x19367e058 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x19367c91c __CFRunLoopRun + 1208
6 CoreFoundation 0x19367be0c CFRunLoopRunSpecific + 608
7 CFNetwork 0x198b15890 0x1988b5000 + 2492560
8 Foundation 0x1947a8520 __NSThread__start__ + 716
9 libsystem_pthread.dylib 0x19359ef94 _pthread_start + 136
10 libsystem_pthread.dylib 0x193599d34 thread_start + 8

Thread 9:
0 libsystem_pthread.dylib 0x193599d20 start_wqthread + 0

Thread 10:
0 libsystem_pthread.dylib 0x193599d20 start_wqthread + 0


Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x00006000002037e0 x1: 0x00000001f3aa27b3 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x0000000000000003 x5: 0x0000000000001420 x6: 0x407f400000000000 x7: 0x0000000000000000
x8: 0x0000008880080000 x9: 0x0000000000000007 x10: 0x0000000152ac20b3 x11: 0x000000000000007f
x12: 0x0000000000000033 x13: 0x000000015a2ac720 x14: 0x010d0001fb2cc301 x15: 0x00000001fb2cc300
x16: 0x0000008880080000 x17: 0x6ae16000002037e0 x18: 0x0000000000000000 x19: 0x0000600000731420
x20: 0x000000016d755710 x21: 0x0000000000000018 x22: 0x0000000000000003 x23: 0x000000016d755630
x24: 0x0000000000000001 x25: 0x000000016d755688 x26: 0x00000001fcd08000 x27: 0x00006000011ca3d0
x28: 0x0000000000000000 fp: 0x000000016d755700 lr: 0x0000000194786d34
sp: 0x000000016d755630 pc: 0x00000001931ce000 cpsr: 0x00001000
far: 0x0000000000000000 esr: 0x72000002 Address size fault

 

[svenmany]

I'm not a macOS developer, so I'm just guessing. It looks like the crash is happening when reacting to a display change. Maybe that means some kind of event from your monitor. Do you have a different monitor to try?

 

[kagharaht]

I'm not a macOS developer, so I'm just guessing. It looks like the crash is happening when reacting to a display change. Maybe that means some kind of event from your monitor. Do you have a different monitor to try?

All I have open is Mail, iMessage and Safari. I wasn't even doing anything but reading a web page. Then that Crash message came up. I only have an iMac M3, Silver, 24gb RAM, 2TB, 8/10 and 4 port. I don't have any monitors attached. TM backup drive and a couple of spinner HD attached. I was just reading a web page. Not even scrolling or doing anything. So I got frustrated with this stupid error.

Because I have things simple, I just did the "Erase" Mac and start all over again. I read here that it's the same as Restoring with the old INTEL way or rebooting command R and erasing the HD. So I just did it and setting things back up. Only have a couple of apps to load and the Printer to set up. I won't even load the driver for now. I'll just use AirPrint for now. Keep the iMac as clean as possible to see if this stops. I won't even modify anything in Mail for now, just leave it as is with default setup. This all started with 14.4.1.

 

[kagharaht]

I see Java on the list there. I do have the latest Java installed with Rosetta installed by Mac OS during installation. I wonder if it's Java doing that? I don't know, just grasping at straws. lol

 

[Bigwaff]

I don't know, just grasping at straws.

If you have a VPN client or service installed, uninstall it. PAC is automatic proxy configuration process. Perhaps some networking software you may have installed left behind some proxy configuration. Review your Settings > Network all active and previously used interfaces "Details" page and verify "Automatic proxy configuration" is turned off.

 

[kagharaht]

If you have a VPN client or service installed, uninstall it. PAC is automatic proxy configuration process. Perhaps some networking software you may have installed left behind some proxy configuration. Review your Settings > Network all active and previously used interfaces "Details" page and verify "Automatic proxy configuration" is turned off.

Thanks but I’ve never used VPN. That’s a good suggestion though.

So i did the Erase Mac thing and started up from scratch again. No TM Restore. Since everything I have is in iCloud. I redownloaded the Apple Apps Pages, Numbers, Keynote. Then Pixlemator Pro. Make MKV, Handbrake, Libre Office, Java from Oracle, Mactracker.

The iMac M3 has no external monitors attached. 1 TM USB spinner. 2 USB external drives. Satechi Dock with 2TB ssd in it. BT Trackpad and Keybaord that came with the iMac. I even connected the Canon Color Laserprinter with AirPrint. I’ll load the drivers and software later if things are stable.

That’s about it. Nothing else installed. It’s restoring my iCloud stuff I’m sure it will finish by tonight syncing with the iCloud data.

If Mail keeps crashing. I’ll just have to remember to open the mail to update it, then quit Mail once a day. I’ll use the iPad and iPhone to send and receive. Maybe the next Mac OS update will fix it. Maybe a bug particular to my iMac and it just hates me. 😬

 

[svenmany]

Thanks but I’ve never used VPN. That’s a good suggestion though.

So i did the Erase Mac thing and started up from scratch again. No TM Restore. Since everything I have is in iCloud. I redownloaded the Apple Apps Pages, Numbers, Keynote. Then Pixlemator Pro. Make MKV, Handbrake, Libre Office, Java from Oracle, Mactracker.

The iMac M3 has no external monitors attached. 1 TM USB spinner. 2 USB external drives. Satechi Dock with 2TB ssd in it. BT Trackpad and Keybaord that came with the iMac. I even connected the Canon Color Laserprinter with AirPrint. I’ll load the drivers and software later if things are stable.

That’s about it. Nothing else installed. It’s restoring my iCloud stuff I’m sure it will finish by tonight syncing with the iCloud data.

If Mail keeps crashing. I’ll just have to remember to open the mail to update it, then quit Mail once a day. I’ll use the iPad and iPhone to send and receive. Maybe the next Mac OS update will fix it. Maybe a bug particular to my iMac and it just hates me. 😬

Perhaps Apple support can help. It's a tough one since you can't recreate it on demand. In all reports you posted, it's the main thread that crashes with things on the thread like (I'm paraphrasing)

"_NSCGSDisplayConfigurationMaximumHDRValueChangedNotificationHandler" - some display value changed - which called
"_reactToDisplayChanges" - we'd better react to the change - which called
"_displayChangedSoAdjustWindows" - we'd better adjust windows - which called
"_NSKeyValueObservationInfoGetObservances" - which tries to tell everyone who cares about the change

This is probably all completely normal during running of mail, but maybe Apple support at a higher tier could confirm that.

I really am guessing and might be embarrassing myself, but that display change is trying to notify observers and crashing while trying to get the class of one of them. Here's someone on iOS having an issue like this https://github.com/flutter/flutter/issues/96849. Someone speculated that a video player plugin failed to remove itself as an observer and was causing the crash. But, you said you have no plugins or extensions installed, so if this is the situation in your case, it would be Apple code leaving a defunct reference to an observer, and that observer is no longer in memory. If something has been removed from memory, that memory could then be off limits. Trying to access that memory would cause the exact crash you're seeing - EXC_BAD_ACCESS. https://developer.apple.com/documentation/xcode/exc_bad_access.

I know you shouldn't have to do it, but you might try a different email client. I've used Thunderbird in the past since it's free, but there are a bunch of email clients that people like.

You mentioned that you see Java in that listing. I don't see that. I do see JavaScript, which is different, but I don't see that in the crashed thread. It's very unlikely that Java would be the cause of this.

 

[kagharaht]

Don't be embarrass, you're a lot smarter than me! LOL...Your assessment about the display change looks logical and something in the OS is not liking that change. Good suggestion with the mail client and from others. I'll definitely keep that as my next move if this thing fails.

I did the erase the iMac and started from scratch. I still feel weird with that procedure is the same results with the INTEL version of "command r" and erase HD and reinstall Mac OS method. I hope this is really a clean install. If it keeps happening with just what I installed then it's a nasty Mail App/OS bug.

Anyway when it says maintain the OS system installed doesn't it get messed up when Mail keeps crashing? Or is that OS never modified with this crash? It doesn't tell me on that page if it's an OS from where? When I update to 14.4.1? I don't know if its keeping a messed up OS or clean?

Erase your Mac and reset it to factory settings - Apple Support

Use the Erase All Content and Settings feature to quickly and securely erase all settings, data, and apps, while maintaining the operating system currently installed.

support.apple.com

 

[svenmany]

Don't be embarrass, you're a lot smarter than me! LOL...Your assessment about the display change looks logical and something in the OS is not liking that change. Good suggestion with the mail client and from others. I'll definitely keep that as my next move if this thing fails.

I did the erase the iMac and started from scratch. I still feel weird with that procedure is the same results with the INTEL version of "command r" and erase HD and reinstall Mac OS method. I hope this is really a clean install. If it keeps happening with just what I installed then it's a nasty Mail App/OS bug.

Anyway when it says maintain the OS system installed doesn't it get messed up when Mail keeps crashing? Or is that OS never modified with this crash? It doesn't tell me on that page if it's an OS from where? When I update to 14.4.1? I don't know if its keeping a messed up OS or clean?

Erase your Mac and reset it to factory settings - Apple Support

Use the Erase All Content and Settings feature to quickly and securely erase all settings, data, and apps, while maintaining the operating system currently installed.

support.apple.com

Most of the OS provided by Apple cannot be written to when you're using the Mac. However, some things and certainly anything that is unique to your user account could be. I assume they meant the read-only OS stuff when they said it maintains the system installed.

 

[svenmany]

I wonder if some of the third-party applications you've installed could be causing this. I don't think it's Java, but I guess the others could have some bug. I don't know which of them might try to hook into display/mail events.

Did you see this crash before installing these applications?

 

[kagharaht]

I wonder if some of the third-party applications you've installed could be causing this. I don't think it's Java, but I guess the others could have some bug. I don't know which of them might try to hook into display/mail events.

Did you see this crash before installing these applications?

Never seen this crash before until 14.4.1. Probably around the first week of April then a few days later I posted it on this forum. All these apps were already running in my iMac

 

[djcraze]

Do you have any mail messages still hanging around since the first week of April (in trash, archive, inbox, anywhere really). I'm sure you do. Most people do. I'm wondering if there's a particular message that Mail is getting hung up on. Have you tried:

1. Removing your iCloud account from Mail
2. Creating a new gmail account
3. Adding that to mail

And seeing if the issue still happens? It'd be annoying since you won't have access to your mail. But it would rule out some things.

Since you have an M3, I'd say give Apple Support a call, or send them an email from support.apple.com.

 

[kagharaht]

Do you have any mail messages still hanging around since the first week of April (in trash, archive, inbox, anywhere really). I'm sure you do. Most people do. I'm wondering if there's a particular message that Mail is getting hung up on. Have you tried:

1. Removing your iCloud account from Mail
2. Creating a new gmail account
3. Adding that to mail

And seeing if the issue still happens? It'd be annoying since you won't have access to your mail. But it would rule out some things.

Since you have an M3, I'd say give Apple Support a call, or send them an email from support.apple.com.

After I did the restore to factory settings I'll try that. I did clean up inbox, trash, junk, archive. All empty now. I do have a gmail account. If it crashes again, I'll do that. Signet of iCloud mail and set up my gmail account and see what happens. I can always get my @Mac.com mail on my iPhone and iPad.

 

[svenmany]

After I did the restore to factory settings I'll try that. I did clean up inbox, trash, junk, archive. All empty now. I do have a gmail account. If it crashes again, I'll do that. Signet of iCloud mail and set up my gmail account and see what happens. I can always get my @Mac.com mail on my iPhone and iPad.

You can automatically forward new iCloud emails to your other account. That can be set up on the iCloud website.

Calling Apple is definitely a good step if you have the time. It will probably take some escalation over a few calls. Anyone running Apple software is supported by them if there's a software issue; you don't need Apple warranty coverage. If there's a hardware issue, then the Apple warranty comes into play. I think you are having a software issue.

I've always suspected some particular email is being processed that is causing the crash. Some content in an email could be triggering a handler that has been improperly registered with Mail. Perhaps "improperly" is too strong a word. Maybe it's been registered in a way that's not compatible with some change in macOS 14.4.1. But, I don't know if third-party applications are allowed to do this, so it might just be an Apple handler that is rarely triggered for other users.

What would care about the display change we see in your stack trace? Something that is responsible to display a portion of an email (or maybe even a subject line) would. Some uncommon content in an email could be the source of the problem.

I don't think that code at the top of the listing is open source. There might be something to learn there that would have helped narrow things down. But, if your problem makes its way as high as an Apple engineer, then they would be able to check it.

 

[kagharaht]

Aha I found my message when it first crashed. Now I remember how much chaos 14.4 update did to my iMac. The BT stopped working, keyboard keys didn't work right, even loading DVD on the iMac the icon would not show up on the desktop but the description would. Only after I did the Factory reset recently of the iMac the DVD/BR icons now show up when I load it.

Does MacOS Sonoma runs fine on your Mac or is it buggy?

After the update, Mail unexpectedly quit. I suspect it was checking mail on its own in the background and something wasn't happy and it quit. I entered my comment and hit the button, it launched back up and works fine now. I did reboot to make sure and clear out and crap though.

forums.macrumors.com

And QuickTime and screen got messed up. it was 14.4 update

Does MacOS Sonoma runs fine on your Mac or is it buggy?

Weird, I just did Mac Diagnostic on the iMac M3 and then Safe Mode. Found the instructions on Apple.com. Because of that Quicktime crash that turned the screen pink and rebooted the Mac, I figure I better run it just in case. After the Mac rebooted and signed in, the BT Keyboard Setup came up...

forums.macrumors.com

 

[kagharaht]

I'll probably JYNX myself here. May 6 I did the erase all content factory reset and so far doing everything I normally do Mail has not crashed. The Magic Trackpad also is smoother. It rarely jumps now. So after posting this, I hope mail doesn't crash again! haha

 

[svenmany]

I'll probably JYNX myself here. May 6 I did the erase all content factory reset and so far doing everything I normally do Mail has not crashed. The Magic Trackpad also is smoother. It rarely jumps now. So after posting this, I hope mail doesn't crash again! haha

I've read that you're never supposed to announce that during the first trimester.

 

[kagharaht]

Update: May 6 is when I did the Erase All Contents and settings. Set up the iMac New. I did not migrate Time Machine Data. I did not copy any files from external drives or App Installers. I have only ONE email account "iCloud.com". I sync everything back from iCloud Drive or services.

I'm probably gonna really JINX myself here 😬 but Mail has not unexpectedly quit on me. I have the Mail App open 24/7 and doing all the stuff I normally do as before. I think the Erase All Contents and Settings and new setup fixed it!

 

[Marc D.]

In this case I do not think PAC means Proxy Automatic Configuration, but rather Pointer Authentication Codes.
See : https://developer.apple.com/documen..._your_app_to_work_with_pointer_authentication