Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

tonyberinson

macrumors regular
Original poster
Jul 19, 2008
101
35
Hey

Has anyone had a problem with the Beta where you try and print from MacMail and mail crashes when the print starts?

I am getting this error.. not sure if anyone can read it. It was working fine in Beta 7 and now its screwed in beta 8.. .

Geez its still so buggy and they are releasing it soon?? Geez I won't be upgrading if this keeps happening..



Process: Mail [1337]
Path: /System/Applications/Mail.app/Contents/MacOS/Mail
Identifier: com.apple.mail
Version: 13.0 (3594.4.2)
Build Info: Mail-3594004002000000~5
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Mail [1337]
User ID: 501

Date/Time: 2019-09-21 10:21:13.096 +0800
OS Version: Mac OS X 10.15 (19A558d)
Report Version: 12
Bridge OS Version: 3.0 (14Y905)
Anonymous UUID: 249E86C7-CC32-8156-5E34-556A69CB6EEF


Time Awake Since Boot: 110 seconds

System Integrity Protection: enabled

Crashed Thread: 21

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00006b10a4d91e90
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1337]

VM Regions Near 0x6b10a4d91e90:
MALLOC_NANO (reserved) 0000600008000000-0000600020000000 [384.0M] rw-/rwx SM=NUL reserved VM address space (unallocated)
-->
STACK GUARD 000070000431b000-000070000431c000 [ 4K] ---/rwx SM=NUL stack guard for thread 19

Application Specific Information:
dyld3 mode
£‰Ãêˇˇ

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6cdf3f76 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6cdf44dc mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff3588d44b __CFRunLoopServiceMachPort + 322
3 com.apple.CoreFoundation 0x00007fff3588c9e7 __CFRunLoopRun + 1695
4 com.apple.CoreFoundation 0x00007fff3588c0c3 CFRunLoopRunSpecific + 499
5 com.apple.HIToolbox 0x00007fff34419f2d RunCurrentEventLoopInMode + 292
6 com.apple.HIToolbox 0x00007fff34419c6d ReceiveNextEventCommon + 600
7 com.apple.HIToolbox 0x00007fff344199f7 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8 com.apple.AppKit 0x00007fff32ac3ee4 _DPSNextEvent + 990
9 com.apple.AppKit 0x00007fff32ac2c50 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
10 com.apple.AppKit 0x00007fff32abd395 -[NSApplication run] + 658
11 com.apple.AppKit 0x00007fff32aaf1c6 NSApplicationMain + 777
12 libdyld.dylib 0x00007fff6ccab2a5 start + 1

Thread 1:
0 libsystem_pthread.dylib 0x00007fff6ceb45b4 start_wqthread + 0

Thread 2:
0 libsystem_pthread.dylib 0x00007fff6ceb45b4 start_wqthread + 0
 

tonyberinson

macrumors regular
Original poster
Jul 19, 2008
101
35
Phew so its not just me - Apple has broken another bread and butter system.
 

Iluvatar1981

macrumors newbie
Sep 13, 2019
18
7
Same here! Both Mail and Safari crash when printing. The strangest thing is that, both are printing first and crashing next. Very nice! We all appreciate the good work from Apple. That's true. There' s nothing we can do but to admit it. When it'll be ready for release? In October? Oh... Jesus!
 
  • Like
Reactions: tonyberinson

btdpi007

macrumors member
Jun 9, 2009
46
6
North Carolina
I don't have much to add here, but I am affected too. Whether I print to a printer or print to pdf, Apple Mail crashes every time. I have noticed several apps also "crash" after I close them, as well. The app closes but I get the crash dialogue box. This is under Beta 8, and I had no issues, I recall, from Beta 1 through 7.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.