When there is a lot of disk activity, VsChromium will sometimes perform a full file system rescan. The reason is that the internal buffer size used for File Change Notification is limited to 60KB. When there is a lot of disk activity, the buffer is not large enough, and file changes are missed.
VsChromium detects that occurrence and initiates a full file system rescan (as opposed to an incremental one) as a safety measure, since it does not know exactly what happened on disk.
The (obvious in insight) solution is to increase the buffer size, which seems to work, even though the .NET documentation mentions to maximum buffer size is 65KB. Experiment with a 2MB buffer not only worked, but also eliminated all occurrence of buffer overflowing.
When there is a lot of disk activity, VsChromium will sometimes perform a full file system rescan. The reason is that the internal buffer size used for File Change Notification is limited to 60KB. When there is a lot of disk activity, the buffer is not large enough, and file changes are missed.
VsChromium detects that occurrence and initiates a full file system rescan (as opposed to an incremental one) as a safety measure, since it does not know exactly what happened on disk.
The (obvious in insight) solution is to increase the buffer size, which seems to work, even though the .NET documentation mentions to maximum buffer size is 65KB. Experiment with a 2MB buffer not only worked, but also eliminated all occurrence of buffer overflowing.