Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VsChromium sometimes performs a full file system rescans during heavy disk activity #41

Closed
rpaquay opened this issue Dec 22, 2017 · 0 comments

Comments

@rpaquay
Copy link
Contributor

rpaquay commented Dec 22, 2017

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.

@rpaquay rpaquay changed the title Too many full file system rescan with heavy disk activity VsChromium sometimes performs a full file system rescans during heavy disk activity Dec 22, 2017
rpaquay added a commit that referenced this issue Dec 22, 2017
This dramatically decreases the number of OverflowException on
heavily changing file system (i.e. during a build) at the cost
of some memory (2 MB instead of 60 KB).

Fixes bug #41
@rpaquay rpaquay closed this as completed Dec 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant