Taiga hangs detecting file info over network share

[sunjayc]

I sometimes watch anime from a network share being served (unfortunately) over a wifi connection. I have noticed that Taiga will become very unresponsive when I am playing anime from this share.

Some debugging seems to indicate that the problem lies with the GetFinalPathNameByHandle Windows API call, which makes network requests to resolve the filename and consequently causes Taiga to hang.

[erengy]

Thanks for the debug. How long does it take for Taiga to resolve the filename? If it doesn't hang indefinitely, moving media detection to a separate thread (similar to #371) may help.

[lunyx]

I have the same issue, though I haven't debugged at all. All of my files are stored on a network share, also served over a wifi connection. Attempting to refresh files available, as well as starting up the client, takes me several minutes. Is the file availability state stored when shutting down? If not, saving that in addition to moving media detection to a separate thread would be useful.

[FreezyLemon]

I'll add that scan performance seems to be worse on any kind of network share. For example on a SATA HDD my library takes around 1 second to scan (talking about a manual F5 scan). The same library on a local network share (1Gb LAN) takes around 15 seconds.

Network usage while scanning is around 3-5Mbit/s, so this is not a bandwidth issue. Maybe some overhead or latency on the network access? Might take a look myself, can't really help with multithreading though.