Open TCB13 opened 1 year ago
Suggesting a rename to 'Potential memory leak in library indexing'
Suggesting a rename to 'Potential memory leak in library indexing'
Thank you for your message. While it is possible that the high RAM usage is related to the library indexing it can simply be because this is an Electron App. :)
However, as I've observed the app using much less memory at that other time, it may be worth investigating if there's anything else contributing to the higher usage. As I said, at some point it was playing music and only using 37 MB.
Those are my values too. If it doesn't play a song it stays at 170MB. When playing a song, it already takes over 200MB
Here is one more strange thing. I ordered a rescan of my library and was using just 30M while scanning.
Restarting the program caused it to go back to around 200M.
Hello,
Thank you this great, modern player build with solid technologies. Now, at the first launch it indexed my music and this was what the RAM usage was looking:
After restarting the program it went down to something very low:
I played around a bit and it went to around 200MB again.
Since it was able to play a song using 30MB, I guess there's something leaking somewhere. Thank you.