Lowlander wrote: ↑Mon Jul 20, 2020 8:48 pm
I'm unable to reproduce on either a local or NAS storage location. MediaMonkey isn't warning about unavailable files in either scenario.
Try replicating when the MM5 window is buried underneath something else during the add/scan operation.
I am intentionally opening the Chrome browser over the top of MM5 when it is doing long batch functions like Add\Scan or track downloads, or library syncs ... I am doing this because I intermittently see a situation where MM5 deadlocks because it opens the modal end of scan dbox, underneath
the main main MM5 window, and the only way out is to end MM5 via the Task Manager ... I am doing this so I can study the situation more before reporting that other issue (again).
My new theory (for the issue this thread is about) is that maybe a MM5 has queued up a scan of my NAS location in a thread that is also waiting to display the end of scan dbox ... and the thread blockage is causing the timeout I am seeing ... the two times that I have seen this issue has been with this new MM5 release, and each time when I raised MM5 to the top of the z-order, it displayed the end of scan dbox, and immediately followed with the lost tracks dbox that I am reporting.
I tried to create the debug log that you suggested, but MM5 crashed while running this 3rd add/scan. ... I tried to send the debug log, but your submission server appears to be down again. ... I did have debug running ... this is where it crashed
It is showing a write lock timeout this time. ... Not my NAS btw, I was adding a directory from a local drive with this add/scan operation.