-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blissify init killed by oom-kill #56
Comments
Hi @jcorporation! I've tried some of what you're suggesting here #58, |
Thank you! The new song fetching attempt works flawlessly. Have you seen that I changed the initial bug report? The issue is not the song fetching, but the memory usage of blissify. I tested it again and the memory usage increases until the kernel oom-killer kills the blissify process. Edit: You can safely increase the search window. I use 10.000 for myMPD without issues. |
Ah damn, I didn't see. It still OOMs then even in |
exact. It seems you forget to free an object in a loop. The memory usage steadily grows. In the logs are also some analysis errors. I do not know if they matter, only for completeness. |
How many songs do you have? I just tried to reproduce by cloning some songs so I reach 150k songs on MPD, but the memory usage stayed the same. I'm trying to pinpoint the issue, because I am not sure where it is coming from :) |
The issue occurs after a few hundred of songs analyzed. At the moment I have no access to my laptop with the installation and access to the music directory. If it helps: It runs the latest x86 Ubuntu version. |
I tried to reproduce, but I can't find memory steadily increasing (it just spikes from time to time but that's because we load songs directly in memory) - when you have access to your library again, could you try to run |
Running blissify with Thanks for your help! |
By default blissify uses all the cores in the system, yes :) Cheers! |
Hi,
I am the developer of myMPD and I find blissify interesting and I would play around with it.
I have tried to test it and my kernel oom-killer terminates
blissify init
. The machine it is running has 16GB of ram.I thought before it was a MPD timeout...
Blissify log:
MPD log:
Kernel log:
The text was updated successfully, but these errors were encountered: