app crashed in the middle of ppl dancing

I had a crazy crash in the middle of a packed dance floor 10 mins. into a set . I am soooo upset . This didn’t happen with the old app . Why is this happening ???

pls tell me why this happened and what I can do to resolve this

I am running a MacBook Pro 2020 M1 chip with Sonoma 14.3
8 GB Ram
512 GB SSD

I’m sorry to hear that, I have never actually had a crash just one deck momentarily stop and I just pressed play again,

What exactly happened and did you have to restart the app?
Did you continue playing without any further crashes?

1 Like

Translated Report (Full Report Below)

Process: djay Pro [776]
Path: /Applications/djay Pro.app/Contents/MacOS/djay Pro
Identifier: com.algoriddim.djay-iphone-free
Version: 5.1 (57691)
App Item ID: 450527929
App External ID: 863291486
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-02-10 23:08:11.9961 -0500
OS Version: macOS 14.3 (23D56)
Report Version: 12
Anonymous UUID: 05C8BBE5-6B2B-F495-93BC-A50ED2DB67D4

Time Awake Since Boot: 9800 seconds

System Integrity Protection: enabled

Crashed Thread: 7 CVDisplayLink

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

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

VM Region Info: 0xc6745d512c0 is not in any region. Bytes after previous region: 13156656419521 Bytes before following region: 91915423509824
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
commpage (reserved) 1000000000-7000000000 [384.0G] —/— SM=NUL …(unallocated)
—> GAP OF 0x5f9000000000 BYTES
MALLOC_NANO 600000000000-600020000000 [512.0M] rw-/rwx SM=PRV

Thread 0:: Dispatch queue: com.apple.main-thread
0 ARGLKit 0x106331ef0 -[ARGLFramedString needsContentRecreation] + 0
1 ARGLKit 0x1063316d0 -[ARGLFramedString newRecreateContentsIfNeededWithMVMatrix:projMatrix:viewPort:] + 96
2 djay Pro 0x104b7f804 0x104b64000 + 112644
3 ARGLKit 0x106331a8c -[ARGLFramedString recreateIfNeededOnMainThread] + 80
4 libdispatch.dylib 0x18601acb8 _dispatch_call_block_and_release + 32
5 libdispatch.dylib 0x18601c910 _dispatch_client_callout + 20
6 libdispatch.dylib 0x18602afa8 _dispatch_main_queue_drain + 984
7 libdispatch.dylib 0x18602abc0 _dispatch_main_queue_callback_4CF + 44
8 CoreFoundation 0x1862ecea4 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16
9 CoreFoundation 0x1862aa760 __CFRunLoopRun + 1996
10 CoreFoundation 0x1862a993c CFRunLoopRunSpecific + 608
11 HIToolbox 0x190872448 RunCurrentEventLoopInMode + 292
12 HIToolbox 0x1908720d8 ReceiveNextEventCommon + 220
13 HIToolbox 0x190871fdc _BlockUntilNextEventMatchingListInModeWithFilter + 76
14 AppKit 0x189a88ed0 _DPSNextEvent + 660
15 AppKit 0x18a273eec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716
16 AppKit 0x189a7c37c -[NSApplication run] + 476
17 AppKit 0x189a53640 NSApplicationMain + 880
18 dyld 0x185e4d0e0 start + 2360

Thread 1:
0 libsystem_kernel.dylib 0x186190e68 __semwait_signal + 8
1 libsystem_c.dylib 0x1860702f8 nanosleep + 220
2 libsystem_c.dylib 0x1860790bc sleep + 52
3 djay Pro 0x105051dec 0x104b64000 + 5168620
4 libsystem_pthread.dylib 0x1861ce034 _pthread_start + 136
5 libsystem_pthread.dylib 0x1861c8e3c thread_start + 8

Thread 2:: SentryCrash Exception Handler (Secondary)
0 libsystem_kernel.dylib 0x18618d874 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x18619fcf0 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x1861964b0 mach_msg_overwrite + 476
3 libsystem_kernel.dylib 0x18618dbf8 mach_msg + 24
4 djay Pro 0x10504dfb4 0x104b64000 + 5152692
5 libsystem_pthread.dylib 0x1861ce034 _pthread_start + 136
6 libsystem_pthread.dylib 0x1861c8e3c thread_start + 8

Thread 3:: io.sentry.app-hang-tracker
0 libsystem_kernel.dylib 0x186190e68 __semwait_signal + 8
1 libsystem_c.dylib 0x1860702f8 nanosleep + 220
2 Foundation 0x18742d2c4 +[NSThread sleepForTimeInterval:] + 160
3 djay Pro 0x104ff6e24 0x104b64000 + 4795940
4 Foundation 0x1873aef14 NSThread__start + 716
5 libsystem_pthread.dylib 0x1861ce034 _pthread_start + 136
6 libsystem_pthread.dylib 0x1861c8e3c thread_start + 8

and then I had another crash a few days ago at home without a controller … the other crash happened with a pioneer ddj sx .

Translated Report (Full Report Below)

Process: djay Pro AI [745]
Path: /Applications/djay Pro AI.app/Contents/MacOS/djay Pro AI
Identifier: com.algoriddim.djay-iphone-free
Version: 4.1.10 (51064)
App Item ID: 450527929
App External ID: 858864569
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-02-08 00:00:37.9292 -0500
OS Version: macOS 12.6.7 (21G651)
Report Version: 12
Anonymous UUID: 05C8BBE5-6B2B-F495-93BC-A50ED2DB67D4

Time Awake Since Boot: 730 seconds

System Integrity Protection: enabled

Crashed Thread: 16 Dispatch queue: ALCFileSystemMediaObject (QOS: UNSPECIFIED)

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00005c557ad68ac0
Exception Codes: 0x0000000000000001, 0x00005c557ad68ac0
Exception Note: EXC_CORPSE_NOTIFY

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

VM Region Info: 0x5c557ad68ac0 is not in any region. Bytes after previous region: 101041166518977 Bytes before following region: 4030913410368
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
commpage (reserved) 1000000000-7000000000 [384.0G] —/— SM=NUL …(unallocated)
—> GAP OF 0x5f9000000000 BYTES
MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=PRV

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_malloc.dylib 0x1977d2eb4 nanov2_pointer_size + 0
1 libsystem_malloc.dylib 0x1977d2e78 nanov2_size + 32
2 libsystem_malloc.dylib 0x1977d2c5c free + 148
3 ARMediaLibraryCore 0x102850fc4 -[ALCMediaObject dealloc] + 52
4 ARMediaLibraryCore 0x10291a0e8 -[ALCFileSystemMediaObject dealloc] + 76
5 CoreFoundation 0x197a2ebe0 RELEASE_OBJECTS_IN_THE_ARRAY + 116
6 CoreFoundation 0x197a2eb18 -[__NSArrayM dealloc] + 276
7 ARMediaLibraryCore 0x1028ed5b0 -[ALCMediaGroup .cxx_destruct] + 176
8 libobjc.A.dylib 0x1978558e4 object_cxxDestructFromClass(objc_object*, objc_class*) + 116
9 libobjc.A.dylib 0x19784cb0c objc_destructInstance + 80
10 libobjc.A.dylib 0x19784cab8 _objc_rootDealloc + 80
11 ARMediaLibraryCore 0x102844f74 -[ALCMutableMediaGroup dealloc] + 56
12 ARMediaLibraryCore 0x1028c188c -[ALCFileSystemFileSearchOperation .cxx_destruct] + 56
13 libobjc.A.dylib 0x1978558e4 object_cxxDestructFromClass(objc_object*, objc_class*) + 116
14 libobjc.A.dylib 0x19784cb0c objc_destructInstance + 80
15 libobjc.A.dylib 0x19784cab8 _objc_rootDealloc + 80
16 Foundation 0x198967c68 -[NSOperation dealloc] + 264
17 ARMediaLibraryCore 0x1028c0c54 -[ALCFileSystemFileSearchOperation dealloc] + 88
18 libsystem_blocks.dylib 0x1976eaa14 _Block_release + 192
19 libdispatch.dylib 0x1978001b4 _dispatch_client_callout + 20
20 libdispatch.dylib 0x19780e6cc _dispatch_main_queue_drain + 928
21 libdispatch.dylib 0x19780e31c _dispatch_main_queue_callback_4CF + 44
22 CoreFoundation 0x197ad2968 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16
23 CoreFoundation 0x197a8fbd8 __CFRunLoopRun + 2532
24 CoreFoundation 0x197a8ea54 CFRunLoopRunSpecific + 600
25 HIToolbox 0x1a06d3338 RunCurrentEventLoopInMode + 292
26 HIToolbox 0x1a06d30b4 ReceiveNextEventCommon + 564
27 HIToolbox 0x1a06d2e68 _BlockUntilNextEventMatchingListInModeWithFilter + 72
28 AppKit 0x19a5f74b8 _DPSNextEvent + 860
29 AppKit 0x19a5f5db0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1328
30 AppKit 0x19a5e7f7c -[NSApplication run] + 596
31 AppKit 0x19a5b9698 NSApplicationMain + 1132
32 dyld 0x101b5108c start + 520

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

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

Thread 3:
0 libsystem_kernel.dylib 0x19798a04c __semwait_signal + 8
1 libsystem_c.dylib 0x197892fc8 nanosleep + 220
2 libsystem_c.dylib 0x19789db78 sleep + 52
3 djay Pro AI 0x100c81bdc 0x1004ac000 + 8215516
4 libsystem_pthread.dylib 0x1979c426c _pthread_start + 148
5 libsystem_pthread.dylib 0x1979bf08c thread_start + 8

Thread 4:: SentryCrash Exception Handler (Secondary)
0 libsystem_kernel.dylib 0x197986890 mach_msg_trap + 8
1 libsystem_kernel.dylib 0x197986d00 mach_msg + 76
2 djay Pro AI 0x100c8d6e4 0x1004ac000 + 8263396
3 libsystem_pthread.dylib 0x1979c426c _pthread_start + 148
4 libsystem_pthread.dylib 0x1979bf08c thread_start + 8

I was using crossfader function in djay pro 5 and pioneer controller DDJ SX when the crash happened last night … the floor cleared out when the crash happened and when I restarted the app , I only ran it for 2 mins or so bc the ppl started to leave :frowning: I updated bc a few days ago the older version crashed right away at home as soon as I opened the app … I have attached both bug reports… im super upset that this happened . this was the first time the app crashed in the middle of a set for me … I have had crashes at home without a controller , but I don’t really care when it happens at home

1 Like

I have also had just one deck momentarily stop a few times but that’s not as bad as the entire app crashing … so I am not too upset about the monetary stoppage but the whole app crashing is an entirely diff animal :(((((

@Xten please note, you do not have to post a new message every time you want to add a line or two. You can edit the original post (click the pencil).

1 Like

That’s the issue I have had a few times when using my iPad and Rane One,
Before every set, I shut down all apps and disable bluetooth,
I then perform a hard reset on my iPad and only open the Djay app…

This procedure seems to have fixed my issue

1 Like

Hi @Xten,

Sorry to hear about this. I’ve been in that situation myself so I know how devastating it is. Crash reports are automatically submitted to the engineering and support team, but I wanted to offer some help in the meantime.

  1. Given that you had a crash on the older version of djay Pro before your gig, this makes me think that there’s something else contributing to this issue.
  2. Have you recently updated your macOS, installed new software on your Mac or added any new hardware to your setup? WiFi or Bluetooth ON?
  3. Were you running any other apps or perhaps an iCloud/Time Machine backup when the crashes occurred?
  4. Below is an article on optimizing your Mac for DJing. I follow a very similar checklist on all of my DJing devices: How To Optimise Your Mac For DJing - Digital DJ Tips
  5. Here’s another more recent article for Mac and Windows laptops: How To Optimise Your Mac Or Windows Laptop For DJing In 2024
2 Likes
  1. No new hardware added. Like I said , I did update to Sonoma recently . wifi was off but bluetooth was on.
    3.Wifi was off , but bluetooth was on and no apps/backups were running in the background. In the past I was running djay pro with wifi on and bluetooth on , even a couple of windows open , and it never crashed like this … like I mentioned earlier , it happened when I was using the crossfader fusion , but I don’t know if that caused it or not.

I was not even streaming from Apple Music or tidal , and using my SSD and NOT an external hard drive.

I have 8 GB RAM and ample space on my laptop , so I know it’s not my laptop bc I don’t have crashes on my laptop.

In your vast experience, what version of djay pro is the most stable and what macOS works best. all these new features are cool and all, but I am looking for stability. Stability is the most important thing for me

I don’t know what to do now … can I go back to an older version of the app … and maybe go back to an older OS. I have been a user for a long time and I pay for this every year … I am nervous about djing with dJay pro now :frowning: I did attach and send crash reports earlier

1 Like

Hi @Xten,

  1. Thanks for the additional information. I have forwarded this onto the engineering team as well.
  2. I haven’t really had stability issues with any macOS, iOS or djay version, so I cannot personally recommend anything helpful here other than the laptop optimization tips already shared above.
  3. As for going back to a previous OS or djay Pro version, you can do this using Time Machine on your Mac.
  4. If I hear anything else from the engineering team, I will be sure to share it here as well.
1 Like

I feel for you, Xten. Happening to me, but I’m at home.

Hi @Xten, can you please update to the latest 5.1.2 djay version and test to see if this has solved your issue? Thanks!

1 Like

yes I will do that … and let you know what happens… Thanks

for some reason, It doesn’t give me the option to update in the App Store…weird … I thought the update was released a few days ago… I guess I’ll just have to wait for it to show up … really hoping that this fixes the stability issue… btw , were you guys able to figure out what caused my major crash ? … I really don’t want to switch and I want to recommend this to all my buds… it needs to be stable tho…Thanks

1 Like

Issues with mine also. Deck stopping, performance issues with the rev1 after a couple hours. All at live gigs…

Hey @Five-0, if you create a separate Question or Bug Report topic and provide specific details about the issues you’re experiencing and can try to troubleshoot them with you.

@Xten that seems odd. What region are you in?

  1. On a Mac, open App Store > Updates and hit ⌘ Cmd R to refresh the page.
  2. Make sure that you are signed into the App Store with the same Apple ID that you used to buy the app originally.
  3. Sign out of the App Store (not iCloud) and reboot your device. Then go to App Store > Updates to download the update.
  4. Go to the App Store’s Today tab > user icon > Purchased and then search for Things in your list of purchases.

Is this still happening after the latest update?

Hi @Xten,

  1. Please use this direct link and let me know if you are able to download the latest djay update: Algoriddim djay for Mac, iPad, and iPhone – The new era of DJing
  2. Also, the crash reports we received, appear to be from 2 different computers running different OS and djay versions.
  3. Both of these crash reports are, unfortunately, incomplete. Can you please contact support directly through the djay app on your Mac via Provide djay Pro Feedback. This will allow us to access the crash reports directly. Please do this for both computers so we can access both crash reports. Thanks!