Other than recent updates for MB, the new 3.0 version of Audacity, and any automatic W10 and Firefox updates, nothing else has changed on these two computers recently. I always have many tabs open in Firefox on both of these computers. During that time, What's My Computer Doing showed that there were still Firefox tasks taking system time and I/O. But it eventually cleared about 5-10 minutes AFTER I shut down Firefox. Just yesterday, I had a major slowdown, so bad that I was contemplating a forced restart in the middle of my work. I MAY have had Audacity running during each slowdown, but I do not think so. I have not traced it to anything specific yet, but MB and Firefox are two apps running that were common to all occurrences. In the past few weeks, I have been experiencing numerous computer slowdowns on TWO computers that I often use at the same time. Just a comment - hope it doesn't throw off this thread, but thought it might provide another data point.
#FIREFOX UPNP PLAYER SOFTWARE#
No other issue with any other software or hardware has been noted. None of this might actually be relevant to my issue but it is the only major change that's been implemented in my way of adding and tagging files since this issue first started.Ĭurrently running. Running the above mentioned regex directly in MB would not work as MB interprets the end of a line in the lyrics field as the last line of the tag while MP3Tag works on an actually line by line basis, if that makes any sense. I don't see how any of these actions could have caused this behavior but I do know that MP3Tag and MB handles lyrics a bit differently. I also made a custom search of a file containing a certain line of lyrics and then I played that file, unrelated to the newly added album above. Lyrics was modified in MP3Tag by running a regex search and replace using this expression: Then I made some changes to the tags with MP3Tag.Īrtwork was added by dragging and dropping from Firefox. The only thing I did yesterday between the time MB was working fine to when it started behaving as described (for the second time) is the following:Īn album was added to the library after being tagged by Picard. Version of MB has been updated 2 or 3 times and this issue has remained A backup of "MusicBeeLibrary.mbl" has been restored Artist pictures from /My Documents/My Music have been removed Everything has been deleted from /Local/Musicbee/InternalCache
Including the one that I believed caused the issue the first time. Every file and folder added in the last two weeks have been removed from my monitored folder. Here's a list of the troubleshooting attempt: This time I feel I've done what I can to solve it but to no avail and I would appreciate some assistance. From one second to another it goes from 450 to 790 and then to 570, on and on and on while the application, as far as I can tell is doing absolutely nothing. It's the fluctuations that bothers me the most as I've never seen that before. CPU usage increases from 0 to 12-13 and the memory keeps fluctuating between 400 and 800 mb. I launch the application, wait about 30 seconds and then it starts going haywire. To make it behave the way it does I don't have to anything. MB ran fine for a little more than a week, I kept on adding/tagging files and listening to music, and then last night the same issue presented itself again. Because that's what software and computers do.
#FIREFOX UPNP PLAYER HOW TO#
I didn't really have a plan on how to deal with it i.e finding out why it was corrupt so I simply moved it from my SSD back to my monitored folder on the NAS, basically repeating the same process I'd gone through 5 minuted earlier, only this time, there was no issue anymore, MB continued to work just as intended and I chose to believe that the problem had just solved itself. After that was done MB worked as intended and the only remaining folder was the one I suspected was corrupt in some way. While moving one of the folders the issue once again presented itself so I sat that folder aside by moving it to another local drive (SSD) while I continued transferring the remaining files and folders back to my monitored folder (NAS). Now the issue disappeared so I began moving the folders back one by one while keeping an eye on the task manager. I did some research suggesting that this might be due to a corrupt file so I moved every file and folder that was added to my monitored folder going back about a month or so to a local drive (HDD).
A few weeks ago while adding files I noticed that MB seemed a bit unresponsive so I checked the process in the task manager and here are 4 examples of the process all taken within 10 seconds:
0 kommentar(er)
