This repository was archived by the owner on Nov 6, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 82
Rename events on PhysicalFileWatcher can throw - Crashing VS. #187
Comments
@NTaylorMullen this shouldn't crash VS no matter what. Did you open a VS bug? |
VS doesn't own any of the code on this stack. The exception never gets caught and ends up crashing VS. |
@ToddGrun hmm then how does it crash VS? |
@Eilon -- An unhandled exception on a background thread will kill VS. |
Ah, background thread, got it! |
@muratg @DamianEdwards should we consider a hot-fix here for RC2 to at least try-catch? And do a better fix for RTM? |
@Eilon yes, I think a simple fix in RC2 is worthy, considering how bad the experience is. |
@muratg can you send email for approval? |
NTaylorMullen
pushed a commit
that referenced
this issue
May 10, 2016
- When enumerating files in the `e.FullPath` directory it's possible to get IO exceptions due to renames, folder structure changes and file locks. This swallows those exceptions. #187
NTaylorMullen
pushed a commit
that referenced
this issue
May 10, 2016
- When enumerating files in the `e.FullPath` directory it's possible to get IO exceptions due to renames, folder structure changes and file locks. This swallows those exceptions. #187
@NTaylorMullen that commit is in to |
Oops pasted the dev commit instead of the release commit (it went into release first). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
In some of Visual Studios test cases when they open a file => new web app 50+ times they eventually encounter crashes here. Essentially
Directory.EnumerateFileSystemEntries
explodes due to a node_modules file being renamed then locked.This is a problem for Visual Studio because it ends up crashing it; however, it is infrequent. This can be mitigated by changing Mvc/Razor to only monitor the Views folder, it currently gets file watcher change events for all of the node_modules folder additions/renames during restore. This can also be fixed across the board by catching around this logic.
Not sure of the severity of this issue.
/cc @Eilon @ToddGrun @pranavkm
The text was updated successfully, but these errors were encountered: