Djay Pro 5.6.9 memory grows to 44.81 GB on macOS

Bug Reports
1

Hi everyone,

I am experiencing a serious and repeatedly occurring memory issue with djay Pro 5.6.9 on my MacBook Pro.

I use djay Pro professionally for live events, including large venues with audiences of up to approximately 3,000 people, so reliability over several hours is absolutely critical for me.

Device Model:
MacBook Pro 13-inch, M1, 2020

Processor / Memory:
Apple M1
8 GB unified memory

Operating System:
macOS Tahoe 26.7.1
The original incidents were documented on macOS Tahoe 26.6.2. The Mac has since been updated to 26.7.1 for further testing.

djay Pro Version:
5.6.9

DJ Controller:
Pioneer DDJ-FLX10

Internal SSD:
Approx. 500 GB total, with more than 50 GB free during the incidents.

A) SUMMARY OF ISSUE

djay Pro initially runs normally and uses approximately 800 MB of memory.

During continued use, the memory consumption increases massively until macOS eventually displays:

“Your system has run out of application memory.”

During the latest documented incident, macOS showed:

djay Pro: 44.81 GB

Finder was using only approximately 392 MB at the same time.

This has now happened repeatedly within a few days.

After force-quitting djay Pro and restarting the Mac, memory usage returns to normal. After restart, djay Pro again uses less than approximately 1 GB.

I therefore have screenshots documenting both states: normal operation at approximately 800 MB and the failure state at 44.81 GB.

B) STEPS TO REPRODUCE

Unfortunately, I have not yet identified one specific action that immediately triggers the issue.

The behaviour appears to develop during continued use:

  1. Start djay Pro normally.

  2. djay initially uses approximately 800 MB of memory.

  3. Continue using djay during a normal DJ session.

  4. Memory consumption starts increasing over time.

  5. Eventually djay reaches several tens of gigabytes of memory usage.

  6. macOS displays the “out of application memory” warning.

  7. djay Pro has to be terminated.

I am continuing to test the system with Activity Monitor open in order to determine how quickly the memory usage increases and whether a particular function triggers it.

C) EXPECTED RESULT

djay Pro should be able to run continuously for several hours without uncontrolled memory growth.

For professional live use, I need to be able to run the software for an entire event without restarting djay Pro or the Mac.

D) ACTUAL RESULT

Memory usage increases from below approximately 1 GB to several tens of gigabytes.

During the latest documented occurrence, djay Pro reached 44.81 GB before macOS reported that the system had run out of application memory.

At that point, continued reliable operation is no longer possible.

PROFESSIONAL IMPACT

This is the part that concerns me most.

I use this setup professionally and sometimes work in venues with audiences of up to approximately 3,000 people.

A DJ application increasing its memory consumption from approximately 800 MB to more than 44 GB during operation is therefore not a minor performance inconvenience for me. It creates a serious risk of software failure during a live performance.

I need this system to remain stable for several hours without intervention.

ADDITIONAL INFORMATION

I found the older 2024 community report concerning a similar memory issue on an M1 Mac with 8 GB RAM running djay Pro 5.1.1. In that case, the user later reported stable operation after updating to 5.1.2.

I am creating a new bug report because this issue is now occurring on djay Pro 5.6.9 and a current macOS version.

I am not assuming that this is necessarily the same bug, but the behaviour appears very similar.

QUESTIONS FOR ALGOriddim

Is this already a known issue in djay Pro 5.6.9?

Are there any known memory-management problems with djay Pro 5.6.9 on macOS Tahoe?

Is there currently a recommended workaround?

Would you recommend staying on macOS Tahoe for a professional production machine rather than upgrading to macOS 27 at this point?

Is there a supported and safe way to roll back to djay Pro 5.6.8 or another previous stable version while this issue is being investigated?

Is there any feature, service or setting that you would recommend disabling temporarily for testing?

I am happy to provide process samples, Console logs, crash reports or any other diagnostic information your development team requires.

I have also submitted this issue directly to Algoriddim Support.

Thanks,

Marcel

05_mac_system_info_serial_redacted
05_mac_system_info_serial_redacted864×1536 303 KB

IMG_0730
IMG_07301920×3413 930 KB

IMG_0731
IMG_07311920×3413 847 KB

IMG_0732
IMG_07321920×1080 310 KB

3

Hi @Marcel_Kuhlen, welcome to the Community! Thanks for such a detailed report and for opening a ticket with Support. Having your setup, the timeline, and both the normal and failure states captured makes this much easier to look into.

Here are answers to your questions:

Known issue? I can’t confirm a known memory issue in 5.6.9 yet. Yours is the first report as far as I know. The 2024 report you found was a leak specific to 5.1.1 that was fixed in 5.1.2. Like you, I wouldn’t assume this is the same bug.

Rolling back to 5.6.8: Algoriddim doesn’t offer older installers. The only way back is to restore the djay Pro app from a Time Machine backup made before you updated. Back up your djay Media Library first so your hot cues and My Collection playlists are safe.

macOS 27: We haven’t published anything about macOS 27 that I can point you to. On a production machine, I’d avoid changing the OS while we’re investigating, since that adds another variable.

What to disable for testing: Change only one thing per session so we can see what matters. Good candidates are Neural Mix, FX (including Crossfader FX), running without the FLX10 connected, and playing local files only instead of streaming.

What would help most:

  1. When djay’s memory climbs past roughly 3 GB, go to Activity Monitor > double-click djay Pro > Sample and attach the result to your support ticket.
  2. A rough log of djay’s memory every 15–30 minutes, with notes on what you were doing at the time.
  3. Your music source (local files, or which streaming service), and whether you use Neural Mix stems, mix recording, or video.
  4. Roughly how many tracks are in your library.
  5. Are you running any other applications or background tasks like a TimeMachine backup our iCloud backup?

For upcoming gigs:

  • Restart the Mac and launch djay fresh right before each set.
  • Keep Activity Monitor open on the Memory tab so you can see growth before it becomes a problem, and plan a djay restart during a break if it starts climbing.
  • Have a backup playback source ready.
  • Turn off automatic updates for djay and macOS on your gig machine.
  • Disable WiFI and Bluetooth if you are using only local music.

I hope that helps, and thanks again for the thorough report!

4

Hello,
I’m having exactly the same problem with a MacBook Pro (2.6 GHz 6-core Intel Core i7, 16-inch, 2019, 16 GB 2667 MHz DDR4) running the latest software version and macOS 26 (no update to macOS 27 available). The difference is that I can’t even start a session because the software launches in the background and ends up consuming… 130 GB of memory. The result is the same as for Marcel Juhlen everything freezes up. I’ve tried just about everything to work around it, but clearly, Djay Pro is no longer compatible with Intel Macs. And, of course, it’s impossible to revert to older versions to keep using my subscription. It’s infuriating.

5

Hi @aml87907, welcome to the Community! Sorry to hear you’re experiencing this issue. Thanks for the setup details - this is very helpful. I fully understand how frustrating this is. I’m currently on the road travelling. Can you please submit an official support ticket through the djay app so someone on our team can look into this further? Thanks!

6

Macbook M1 Max, 32GB, 26.7.1

I also had something that smells like a resource issue. While rehearsing a set, suddenly after maybe 45 minutes, the track detailed view started lagging 16 bars or so behind with updating. The newly started track did not sync correctly. I tried to solve it, so I’m not able to record it, but will if it occurs another time.

Activity monitor showed only 1.59 GB memory usage which seems normal. Funny is that, after decks stopped, DJay still uses 124% CPU, while it should be near idle?

Edit: after playing a bit more, idle is about 50% Cpu, running a set on 2 decks with effects and looper just over 100%.