While dms won't do a full library scan on startup, it does do a full scan once it is first accessed. Seem like this is due a bug in how the childCount property of container objects is calculated when clients make their initial Browse/BrowseDirectChildren call. Currently, this results in a recursion iterating through every folder in the library, including calls to ffmpegProbe on all eligible files. As this is quite time consuming for large libraries, it can lead to clients timing out on the initial Browse call.