(Resolved) Traktor 4 Memory Leak when creating stems
Device: Macbook Pro 16" 2019
OS: Sonoma 14.5
Happens when queueing up a few stems to generate
Comments
-
could you please share some of the tracks you were generating stems for when this happened?
0 -
Hi Allan! Not the OP, but, I have the same problem. I have a M1 MacBook Air with 8gb of memory. I use .flac tracks nearly exclusively and have noticed this problem with most of them.
A simple way to reproduce this behavior is to queue up many tracks. You’ll notice that between each track the memory isn’t completely released. After a while Traktor memory use balloons up like this. The only way to free it is to relaunch the app.
0 -
Thanks, I have managed to observe the same on my end as well, are you also on Sonoma?
0 -
Yep, latest Sonoma.
0 -
alrigh thank you for raising this we are looking into it.
4 -
PC as well.
1 -
To recreate this bug just queue up songs for stem seperation I can reliably recreate this bug every time regardless of tracks being queued. The memory starts to creep almost immediately but to see the very high ram usage queue up about 20 songs for stem seperation and after it processed about 10 or 15 you should see huge jumps in memory usage. I had this get as high as 120gb of memory!!!
2 -
This isssue should only occur on macOS, On windows you will see the inital spike in memory usage during stem separation but after it should return to normal levels.
1 -
That is correct. If you make a big batch of about 100 songs for stem seperation after +/- 50 tracks the stem seperation will stop. You can still save your collection but you can no longer shut down TP4. You’ll get a screen with the message “flushing background tasks” and this will stay there at least for 20 hours. (Then I gave up)
0 -
okay, so if you seperate alot of tracks on windows do you observe this consistently?
0 -
Yes I do. Only if you try to seperate a lot of tracks.
0 -
I had a crash with several stems generating in a batch. My memory got to 100% in use and then Traktor just CTD. Is that something different then?
0 -
I have been able to repo the issue on windows mentioned. It is different from the MacOS memory leak we are looking into it. Thanks to all for the input.
6 -
+1
I queued 36 tracks for stem generation and I am witnessing the memory leak too. Memory usage is now 36,19 GB and rising.
Last night I queued some 164 tracks to generate stems and I found my laptop restarted this morning, no stems generated.
Now I see that it's no wonder that NI didn't include batch process for generating stems…
NI, please sort this out, we trust you, we bought the Traktor 4 update hoping to use this new techonology…
0 -
It seems that Mac's have a limit with page files and so once the memory leak gets big enough it crashes the OS, had the same issue. I wouldn't mind the crashing if it was not for the fact that traktor doesn't save anything at all until the app is closed correctly and so any crash of any kind results in nothing being saved which can be pretty frustrating. I've lots entire set history, days of analyzing and generating stems, and not had settings saved.
0
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 731 Tech Talks
- 3.8K Native Access
- 15.8K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 811 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 6.9K Traktor
- 6.9K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators