DJAY Pro closes unexpectedly as soon as I open it.

I have uninstalled and re-installed several times.

Here is the error below:

Translated Report (Full Report Below)

Process: djay Pro [3311]
Path: /Applications/djay Pro.app/Contents/MacOS/djay Pro
Identifier: com.algoriddim.djay-iphone-free
Version: 5.0.2 (56283)
App Item ID: 450527929
App External ID: 862187883
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-12-18 09:40:06.2216 -0500
OS Version: macOS 14.2 (23C5055b)
Report Version: 12
Anonymous UUID: 0D8207FC-7F45-F420-26E1-F666C787A1A2

Sleep/Wake UUID: EB9F8955-57DF-4134-B4BE-C5BDF132F049

Time Awake Since Boot: 21000 seconds
Time Since Wake: 1260 seconds

System Integrity Protection: enabled

Notes:
PC register does not match crashing frame (0x0 vs 0x7FF80F7037CE)

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

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

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

VM Region Info: 0x8 is not in any region. Bytes before following region: 140723015909368
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
mapped file 7ffca1600000-7ffcc9f88000 [649.5M] r-x/r-x SM=COW …t_id=5fb39af3

Error Formulating Crash Report:
PC register does not match crashing frame (0x0 vs 0x7FF80F7037CE)

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 AppKit 0x7ff80f7037ce 0x7ff80f2ce000 + 4413390
1 AppKit 0x7ff80f5b804e -[NSScrollView _drawOldSchoolFocusRingIfNecessaryInRect:] + 184
2 AppKit 0x7ff80f5b7f8f -[NSScrollView _viewDidDrawInLayer:inContext:] + 112
3 AppKit 0x7ff80ff0881f -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 1882
4 AppKit 0x7ff80f45704a -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 747
5 AppKit 0x7ff80fa29402 -[NSViewBackingLayer drawInContext:] + 64
6 AppKit 0x7ff80f742b81 0x7ff80f2ce000 + 4672385
7 AppKit 0x7ff80f762f6c 0x7ff80f2ce000 + 4804460
8 AppKit 0x7ff80f71785e 0x7ff80f2ce000 + 4495454
9 AppKit 0x7ff80f762a5c 0x7ff80f2ce000 + 4803164
10 AppKit 0x7ff80f760380 0x7ff80f2ce000 + 4793216
11 AppKit 0x7ff80f742acf 0x7ff80f2ce000 + 4672207
12 AppKit 0x7ff80f742bcb 0x7ff80f2ce000 + 4672459
13 AppKit 0x7ff80fa29042 -[NSViewBackingLayer display] + 1763
14 QuartzCore 0x7ff81476ddf5 CA::Layer::display_if_needed(CA::Transaction*) + 867
15 QuartzCore 0x7ff814906a48 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 758
16 QuartzCore 0x7ff81474efa1 CA::Transaction::commit() + 725
17 AppKit 0x7ff80f46808d __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285
18 AppKit 0x7ff80ff4f459 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
19 CoreFoundation 0x7ff80bd9eccc CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 23
20 CoreFoundation 0x7ff80bd9ebf1 __CFRunLoopDoObservers + 493
21 CoreFoundation 0x7ff80bd9e173 __CFRunLoopRun + 850
22 CoreFoundation 0x7ff80bd9d859 CFRunLoopRunSpecific + 557
23 HIToolbox 0x7ff816b549d9 RunCurrentEventLoopInMode + 292
24 HIToolbox 0x7ff816b54616 ReceiveNextEventCommon + 201
25 HIToolbox 0x7ff816b54531 _BlockUntilNextEventMatchingListInModeWithFilter + 66
26 AppKit 0x7ff80f30ca09 _DPSNextEvent + 880
27 AppKit 0x7ff80fc168e4 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
28 AppKit 0x7ff80f2fdf82 -[NSApplication run] + 603
29 AppKit 0x7ff80f2d1f91 NSApplicationMain + 816
30 dyld 0x201743386 start + 1942

Thread 1:: com.apple.rosetta.exceptionserver
0 runtime 0x7ff7ffd44294 0x7ff7ffd40000 + 17044

Thread 2:
0 runtime 0x7ff7ffd6294c 0x7ff7ffd40000 + 141644

Thread 3:
0 runtime 0x7ff7ffd6294c 0x7ff7ffd40000 + 141644

Thread 4:
0 runtime 0x7ff7ffd6294c 0x7ff7ffd40000 + 141644

Hi @motoboat. It looks like you’re running a beta version of macOS 14.2, which contains a known issue causing this crash on launch. We already reported this to Apple, and the issue does not happen in the official macOS 14.2 release.

I’d recommend leaving the macOS beta program and updating to the official macOS 14.2 release.

Hope that helps.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.