by 1337haXXor » Wed May 20, 2020 2:05 am
I reported this problem a while ago, and while I'm happy to report that MM hasn't outright crashed like it used to in a while, it's still increasing memory/CPU usage until it slows my whole computer down. This is solved with exiting and restarting the program, and doesn't SEEM to increase with simply listening to music (only updating the last played and playcount node in the database, I guess?). But if I add a few albums to the library, edit a few tags, do a bit of file moving (I have my music to be sorted in a separate location, add it to MM, edit tags, then auto-organize). All of these have lots of DB edits, and I assume it's what bogs down the system.
I've taken two debug logs. These are after 6 or 7 album addition with all my aforementioned edits/tagging. The first log is when the most recent album was still in the old, un-auto-organized location (an older, slower HDD). The second is after I auto-organized to my main drive (fast SSD). The logs simply show a track finishing, and the next one starting. My RAM usage at this time was sitting at over 1GB, and my CPU during track changing hit 100% for about 3-5+ seconds, sometimes locking my computer during that time.
In addition, this would bring about the other typical(?) glitches, such as forced refreshes, oftentimes which are improper. They display the wrong amount of songs (sometimes an "earlier" number of tracks, like how many I had when I first opened MM in the morning, before adding tracks), visual glitches of reverting tags (showing an album with the old artist name, for example, before I edited that tag), and I recall you guys reporting a fix of no longer showing 2000 or 4000 on refreshes or something? Which is the case, but it seems like the number was just bumped up to 32000, because my library will freeze at that amount often as well. ALL of these visual bugs are fixed 95% of the time by changing to another view (a playlist, device menu, etc.) and then back again. The other 5% of the time I have to do it twice. I don't mean to double stack issues, I can make a separate post if needed. I've had all of these issues before constantly, but they happen increasingly as the program "bogs down" over time.
I'm currently on 2247, but these issues have been persistent pretty much always. Again, the full-on crashes seem to be resolved, but not the general slowing. I generally am on the newest version, though sometimes (such as now) I can get 1 or 2 behind. System is very powerful, and shouldn't be the issue (i7-8700, 16GB RAM).
Log 1 -
http://www.mediafire.com/file/edn3z0aa3 ... S.LOG/file
Log 2 -
http://www.mediafire.com/file/f05p9tp8z ... 2.LOG/fileI reported this problem a while ago, and while I'm happy to report that MM hasn't outright crashed like it used to in a while, it's still increasing memory/CPU usage until it slows my whole computer down. This is solved with exiting and restarting the program, and doesn't SEEM to increase with simply listening to music (only updating the last played and playcount node in the database, I guess?). But if I add a few albums to the library, edit a few tags, do a bit of file moving (I have my music to be sorted in a separate location, add it to MM, edit tags, then auto-organize). All of these have lots of DB edits, and I assume it's what bogs down the system.
I've taken two debug logs. These are after 6 or 7 album addition with all my aforementioned edits/tagging. The first log is when the most recent album was still in the old, un-auto-organized location (an older, slower HDD). The second is after I auto-organized to my main drive (fast SSD). The logs simply show a track finishing, and the next one starting. My RAM usage at this time was sitting at over 1GB, and my CPU during track changing hit 100% for about 3-5+ seconds, sometimes locking my computer during that time.
In addition, this would bring about the other typical(?) glitches, such as forced refreshes, oftentimes which are improper. They display the wrong amount of songs (sometimes an "earlier" number of tracks, like how many I had when I first opened MM in the morning, before adding tracks), visual glitches of reverting tags (showing an album with the old artist name, for example, before I edited that tag), and I recall you guys reporting a fix of no longer showing 2000 or 4000 on refreshes or something? Which is the case, but it seems like the number was just bumped up to 32000, because my library will freeze at that amount often as well. ALL of these visual bugs are fixed 95% of the time by changing to another view (a playlist, device menu, etc.) and then back again. The other 5% of the time I have to do it twice. I don't mean to double stack issues, I can make a separate post if needed. I've had all of these issues before constantly, but they happen increasingly as the program "bogs down" over time.
I'm currently on 2247, but these issues have been persistent pretty much always. Again, the full-on crashes seem to be resolved, but not the general slowing. I generally am on the newest version, though sometimes (such as now) I can get 1 or 2 behind. System is very powerful, and shouldn't be the issue (i7-8700, 16GB RAM).
Log 1 - http://www.mediafire.com/file/edn3z0aa3a0s6sa/LAVOS.LOG/file
Log 2 - http://www.mediafire.com/file/f05p9tp8zkurud1/LAVOS2.LOG/file