.NetCore - FileSystemWatcher on a network drive, unsafe code Win32 API crash

Just a quick update, because I'm still on the way to fix it.

I created a MS Support issue. After many try we just succeed to reproduce it. We had to "play" with the network and simulating some "disturbances". It seems that FileSystemWatcher events didn't been sent as it should be (It's sent by TCP protocol, SMB way). Our team is still working on finding how it can happen..

MS agreed that this shouldn't crash the FileSystemWatcher in some unsafe code no matter if there was a real network issue. So, they just made a PR to add some security around it.

I'm still following the PR but it should be fix in .Net 5 and backported in .Net Core 3.1(.9).

Thanks for the help.

Tags:

C#

Winapi

.Net Core

File Watcher

Related

How to implement fixed version of library to my Android studio project? Fit SVG transformed element into the rect bounds with JavaScript numpy create array of the max of consecutive pairs in another array CSS select all previous siblings for a star rating Exception when trying to upgrade to Kotlin 1.4.10 in Android Studio Type 'State<List<User>?>' has no method 'getValue(Nothing?, KProperty<*>)' and thus it cannot serve as a delegate Rearrange a number into non-English alphabetical order in Raku How can I send an HTTP request from my FastAPI app to another site (API)? change specific values in dataframe if one cell in a row is null Flutter The named parameter 'colors' isn't defined in SweepGradient What is the purpose of a custom React reconciler within a DOM host? Asyncio event loop is closed when using asyncio.run()

Recent Posts