Consistent Crashes Related to Memory Access Issues

Hi there,

I’m experiencing a recurring crash with djay Pro (version 5.2.9, build 61228) on my Mac running macOS 15.3.1. The app crashes with a segmentation fault (SIGSEGV) while interacting with the interface—specifically, it seems to occur during a collapse or expand action on an NSOutlineView.

Here are some technical details from the crash log:

  • Crash Reason: EXC_BAD_ACCESS (SIGSEGV)
  • Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010
  • Faulting Thread: Main thread
  • Top Frame: objc_msgSend called with a null or deallocated pointer
  • Related Frameworks: Foundation, AppKit, likely involving NSMapTable and NSOutlineView

The crash appears to happen here:
-[NSOutlineView _doUserExpandOrCollapseOfItem:isExpand:optionKeyWasDown:]

followed by a message send to a bad address in:
-[NSConcreteMapTable removeObjectForKey:]

This issue has been happening for months and I keep telling y’all there is something wrong with the app, and I keep being told that the team is unable to recreate it. It keeps coming back with the same invalid memory message, where it’s trying to access something in the framework that is not there.

What is going on??

Hi @djsunkisst, thanks for the details about your setup and the issue. This is very helpful. Sorry to hear you’re experiencing this issue. To help us troubleshoot this crash, please submit an Official Support Ticket using the procedure below so the engineering team can review your crash reports in more detail. Please also share the detailed information you provided above.

  1. Open the djay Pro app on your Mac.
  2. In the top left corner of your screen, click on the portion of the menu bar that says “djay Pro”.
  3. In the drop-down menu, click on the button that says “Provide djay Pro Feedback”.
  4. Fill out the submission form that will pop up in your default browser and title your email “ATTN: MARIE – “The Title of your Community Topic” in the provided subject line.

As I don’t have access to your crash reports, unfortunately, there isn’t a lot of additional support that I can provide here. However, please feel free to share any other details about your crashes here that you think will be helpful in diagnosing the issue. I hope that helps!

Thank you for the swift response. I will submit a ticket, but can this please get a little more light from the support team?

The last few times I had this issue, I’ve been told it’s been fixed, or that the team can not recreate it. I think this needs really to be looked a little more deeply. The crashes occur every other event, and as a wedding DJ this is absolutely detrimental. I ran the program today, and as I was searching for a song the program completely crashed. Nothing else was being done other than me searching for one song. Why do I keep having these crashes?

You’re welcome @djsunkisst. I fully understand your frustration. Unfortunately, sometimes these issues are very isolated and directly related to a super specific software/hardware setup combination. So, troubleshooting the issue can be really challenging without being able to replicate it. This is why it is so important to gather as much contributing information as possible to help our teams to replicate the issue, properly diagnose it and ultimately develop a solution. It is very hard to provide a solution if you cannot clearly isolate the problem. I hope that makes sense. Your crash reports should provide some helpful clues though.

EDIT: can you please provide more specific details about your Mac hardware and any other connected DJ hardware including firmware versions? Thanks!

Thank you again for the response, though feel like I am being gaslit here a bit. I am very confident that it’s not a hardware issue. I’ve verified that I am running the the latest driver (4.0.1) for the controller I use, which is a DDJ SR2. And I am experiencing this problem on an brand new M4 Macbook Pro with 24 gigs of RAM, running the most up to date version of Mac OS, and the latest version of Djay software.

I’ve experienced this before on an Intel Mac, decided to upgrade, and still have this issue.

I strongly believe this lies within the code of the program, not what hardware I use.

I posted a video of the incident here:

As you can see, I was just doing a simple search for the next song in my library to play and the program just absolutely failed mid dance floor.

I hope this video sheds more light on this problem and we can come to a resolution.

A little more context, I am going to say again as I’ve repeatedly said before in other reports. It may have something to do with Beatsource. I just checked the last song that was playing at the time of the crash, and what do you know…? It was a Beatsource track.

I’m telling y’all there’s something funky going on with Beatsource!!

Additionally the day before, I did not have a full crash, but I did have a stutter. The program stopped both tracks and I had to hit play again to get them going. Checking my recently played from that night, it also happened with a Beatsource track.

I was playing the Beatsource track on the left, went to mix out of it, hit an effect while fading in the second track ‘Two Dozen Roses’, and the program freaked out, and stopped playing both tracks. I had to hit play two times for it to recover and start playing that second track again.

I am seeing a recurring theme here with Beatsource.

Hi @djsunkisst, thank you for the Mac details along with the video, screenshot and additional context for the crash. This should be very helpful for the engineering team in diagnosing your issue. I have passed on all of the details you shared here to our official support for further review. Thanks again!

EDIT: sorry, I did not mean to imply that I thought your issue was specifically a hardware problem. I was trying to explain why the engineering team was not able to replicate your issue and troubleshoot it previously. Often these isolated issues are related to a specific combination of hardware and software. If the team cannot replicate the issue, it becomes challenging to troubleshoot further.

Given that this seems to be linked to Beatsource, I suspect there could be a corruption within your djaymedialibrary database.

Can you please upload your djay Media Library database file to your Google Drive/Dropbox, enable sharing permissions, then share a link to here or send it to me in a DM?

  • On macOS it can be found in ~/Music>djay. Thanks!

It’s okay, and I apologize. I’ve just been quite frustrated with everything going on with the program. I understand you’re doing the best you can to solve the issue. Here’s the library file on Google Drive:
https://drive.google.com/drive/folders/11jkwhswQHwEypQ5yfLp3weYN5A7dVnyj?usp=sharing

No problem @djsunkisst. I totally understand your frustration. Thanks for the db. I’ve passed it onto engineering for review. I’ll report back here when I have more news. Also, please note that the Official Support team via email is different from the Community Support team here so it’s best to communicate with only one of us so there’s no accidental loss of information.

Good morning, just following up. I haven’t received anything from the support team yet unfortunately. Is there any way this can be escalated up at all? Going into a busy next few weeks of weddings & events, and want to ensure that no more issues arise. Thanks!

Hi @djsunkisst, our engineering team is still investigating this unfortunately. I’ll let you know as soon as I have more information though.

Hi again @djsunkisst, engineering is asking if you deleted any playlists at any point in the session and then hit undo CMD+Z. Please confirm. Thanks!

Hey there! I can confirm that no playlists were being deleted at the time or before the crash. it has happened in the past where I’ve had a crash because of a playlist that I deleted while I was mixing, but not this time. Just scrolling through playlists searching for the next song.

Actually, I may have before arriving to the event if the crash logs show I didn’t restart the program before arriving and setting up. I’m not sure if that can be seen in there. I would have arrived at about 7:30 AM that day, Central Time.

Thanks for the additional info @djsunkisst