You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
The text was updated successfully, but these errors were encountered: