Activity Monitor Crashes Unexpectedly? HELP NEEDED

Question

Activity Monitor Crashes Unexpectedly? HELP NEEDED

For some reason Activity Monitor keeps on crashing; so I tried to keep on opening it. The first few times the app window showed up then terminated by itself, then at like the 4-5th time it showed this(not full version):

Process: Activity Monitor [665]

Path: /System/Applications/Utilities/Activity Monitor.app/Contents/MacOS/Activity Monitor

Identifier: com.apple.ActivityMonitor

Version: 10.14 (1040)

Build Info: ActivityMonitor-1111002000000000~62

Code Type: X86-64 (Native)

Parent Process: launchd [1]

User ID: ***

Date/Time: 2024-06-03 18:56:11.4760 -0700

OS Version: macOS 14.4.1 (23E224)

Report Version: 12

Bridge OS Version: 8.4 (21P4222)

Anonymous UUID: 91***CD3

Time Awake Since Boot: 29 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4

Terminating Process: exc handler [665]

Application Specific Backtrace 0:

0 CoreFoundation 0x00007ff8085b57e6 __exceptionPreprocess + 242

1 libobjc.A.dylib 0x00007ff8080a5e9d objc_exception_throw + 48

2 CoreFoundation 0x00007ff8085b5686 +[NSException raise:format:] + 214

3 AppKit 0x00007ff80bcfd93a -[NSBezierPath(NSBezierPathDevicePrimitives) _deviceLineToPoint:] + 89

4 Activity Monitor 0x000000010e45a449 Activity Monitor + 357449

5 CoreFoundation 0x00007ff808536db7 __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 7

6 CoreFoundation 0x00007ff808536c55 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 290

7 Activity Monitor 0x000000010e459cb3 Activity Monitor + 355507

8 AppKit 0x00007ff80bcf3a5c _NSViewDrawRect + 121

9 AppKit 0x00007ff80c7ab20e -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 1848

10 AppKit 0x00007ff80bcf331a -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 747

11 AppKit 0x00007ff80c2cab54 -[NSViewBackingLayer drawInContext:] + 64

12 AppKit 0x00007ff80bfe2dd1 block_destroy_helper.34 + 17169

13 AppKit 0x00007ff80c002d50 _swift_stdlib_malloc_size + 32642

14 AppKit 0x00007ff80bfb6c7d _swift_stdlib_malloc_size + 3666

15 AppKit 0x00007ff80c00285c _swift_stdlib_malloc_size + 31374

16 AppKit 0x00007ff80c00047e _swift_stdlib_malloc_size + 22192

17 AppKit 0x00007ff80bfe2d06 block_destroy_helper.34 + 16966

18 AppKit 0x00007ff80bfe2e1b block_destroy_helper.34 + 17243

19 AppKit 0x00007ff80c2ca794 -[NSViewBackingLayer display] + 1763

20 QuartzCore 0x00007ff810b3ef15 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 867

21 QuartzCore 0x00007ff810cd6d88 _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 758

22 QuartzCore 0x00007ff810b1fd31 _ZN2CA11Transaction6commitEv + 725

23 AppKit 0x00007ff80bd0434d __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285

24 AppKit 0x00007ff80c7f1e59 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41

25 CoreFoundation 0x00007ff808541fa6 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23

26 CoreFoundation 0x00007ff808541eca __CFRunLoopDoObservers + 493

27 CoreFoundation 0x00007ff80854144c __CFRunLoopRun + 850

28 CoreFoundation 0x00007ff808540b32 CFRunLoopRunSpecific + 557

29 HIToolbox 0x00007ff812f52829 RunCurrentEventLoopInMode + 292

30 HIToolbox 0x00007ff812f52636 ReceiveNextEventCommon + 665

31 HIToolbox 0x00007ff812f52381 _BlockUntilNextEventMatchingListInModeWithFilter + 66

32 AppKit 0x00007ff80bba8be5 _DPSNextEvent + 880

33 AppKit 0x00007ff80c4b8fe9 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1273

34 AppKit 0x00007ff80bb9a005 -[NSApplication run] + 603

35 AppKit 0x00007ff80bb6dff1 NSApplicationMain + 816

36 dyld 0x00007ff8080da366 start + 1942

[Edited by Moderator]

MacBook Pro 13″, macOS 14.4

Posted on Jun 3, 2024 7:04 PM

Reply

Answer 1

BDAqua

Level 10

251,399 points

Jun 3, 2024 9:24 PM in response to DragonFire2271

Start with this...

Safe Boot, (holding Shift key down at startup), does the problem occur in Safe Mode? Could take 10 minutes or more.

Safe mode attempts to repair Disks & clears lots of caches & loads safe Drivers, & prevents loading of 3rd party extensions, so if Safe Mode works try again in regular boot.

To find out if it's system wide or user specific, try this...

Open System Preferences>Users & Groups, unlock the lock, click on the little plus icon, make a new admin account, log out & into the new account.

Does it work in the new account?

Reply

Answer 2

Owl-53

Level 10

111,415 points

Jun 4, 2024 1:30 AM in response to DragonFire2271

Follow previous advise >> First

Just to add

Should this be an Apple Silicon Computer ? the Safe Boot is slightly different from Intel based computers

If you're using a Mac with Apple silicon

Shut down your Mac.
Press and hold the power button on your Mac. As you continue to hold the power button, your Mac turns on and loads startup options. When you see Options, release the power button.
Select your startup disk. It's named Macintosh HD, unless you changed its name.
Press and hold the Shift key, then click the “Continue in Safe Mode” button below your startup disk.
Log in to your Mac. You might be asked to log in again.

One other note - the current version of Sonoma is now version 14.5

Whether this will or will not fix the Activity Monitor - do not know but al least the computer us now up to date

About the security content of macOS Sonoma 14.5

Always make a Time Machine Backup before doing any upDates.

Reply

Activity Monitor Crashes Unexpectedly? HELP NEEDED

Similar questions