Out of Memory
1. If you experienced a crash or other abnormal behavior, please attach the log file 'beaTunes-logs-2023-07-01-135759.zip' by dragging it from your desktop onto the 'Attach File' button below.
2. Please enter your message to us here.
Beatunes is causing my system to run out of memory lately. It often goes beyond the physical 16gb I have on my MacBook Air M1.
* beaTunes: 5.2.32
* JVM: OpenJDK 64-Bit Server VM
* Version: 11.0.17+7-LTS
* Vendor: BellSoft
* OS: Mac OS X 13.4.1, x86_64
* Library: Music.app
* Memory: 92m - 8192m
* Registered as: John Bergman
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by hendrik on 01 Jul, 2023 01:22 PM
Hey John,
that is surprising. How do you know? Do you have some sort of data/screenshot?
Also, how many songs do you have in your library?
Thanks,
-hendrik
2 Posted by John Bergman on 01 Jul, 2023 03:11 PM
I know this because Beatunes is at the top of the list for “Force to quit” for no more system memory warning. It would be inconvenient for me to try to recreate the error at the moment. I have a gig in an hour.
I have exactly 141,220 song files in my collection.
Also, Beatunes has been slower finding duplicates or missing files since I have flattened the folders in my Music folder. Finding duplicates gets stuck at 33.3%, so I let it run overnight.
3 Posted by John Bergman on 16 Jul, 2023 08:59 PM
Anything? No suggestions?
Support Staff 4 Posted by hendrik on 17 Jul, 2023 11:21 AM
Hey John,
sorry for not getting back to you—I'm currently on vacation.
Thanks for that info. That's certainly a fairly large collection.
I guess that means you have hundreds or thousands of tracks in one folder? Can you explain in more detail?
Does letting it run over night help in processing past 33%?
Regarding memory consumption: Because of your collection size, beaTunes allowed itself to use up to 8 GB of real memory for its heap (plus additional segments):
This is probably what's the problem. You can adjust this value manually to something lower, like 6GB or 4GB. How that's done is explained in this article. However, too low a memory setting may lead to other issues. But it's probably worth a try.
After what activity do you see the issue? After inspection, analysis or regular usage without inspection or analysis?
Cheers,
-hendrik
5 Posted by John Bergman on 19 Jul, 2023 09:04 AM
I think it could be a combination of Beatunes and iTunes/Music. Maybe my iTunes library was corrupted. I threw it out and started over. Things seem to be working more smoothly.
iTunes seriously needs some attention but no one seems to care about the app.
Luckily, most of my playlists are in Traktor.
I guess ideally Beatunes might work better without iTunes with a directory based library? The big issue here is that Beatunes lacks the very valuable Smart Playlist feature of iTunes.
In iTunes I create smart BPM lists nested with multiple genres and use those as sources in Beatunes to build my playlists.
Here’s a screenshot for an example:

Support Staff 6 Posted by hendrik on 20 Jul, 2023 11:35 AM
Well, if you run into the memory problem again, you could still try to reduce beaTunes' memory footprint.
Perhaps Apple simply cares about other aspects. 🤷♂️
Not necessarily. If you want Music/iTunes to show any beaTunes analysis results, working with an iTunes/Music-based beaTunes library is highly recommended.
Yes. That's a functionality beaTunes does not have. Matchlists are different and not necessarily deterministic from the user's POV. Perhaps some day in the future, beaTunes can do this, too.
7 Posted by John Bergman on 20 Jul, 2023 12:08 PM
Well my point in bringing up using Beatunes as a stand alone without iTunes is because I think that iTunes is slowing things down. Beatunes is much faster after I deleted the iTunes database and started over.
Support Staff 8 Posted by hendrik on 25 Jul, 2023 11:10 AM
That surprises me, but - oh well - if that's how it is! :-)