Comment 2 for bug 372991

I'm seeing the same issue when my library is at a directory mounted by sshfs. I have turned off all the automatic library scanning settings. When I load up listen, a ton of network traffic take place between my machine and the network drive. This means it takes a long time to start up listen and load my library, and if I close listen before it finishes loading the library, the songs.db database gets corrupt (some songs appear to be removed).

Couple of questions about this: What exactly is being transfered over the network at startup? Are there things that listen needs to discover from files in the library each time it starts that are not located in the songs.db file? Is there a way to store those pieces of information in the db instead?

Great program! This is one of the only things that makes it difficult to use for me...