fork makes Unity deadlock sometimes on Windows

[cannaan]

Windows11, Fork 2.21.0.0
after switch version control to fork, some of my Unity project stuck at the loading splash. recent Unity log says:

Begin MonoManagerReloadAssembly
- Loaded All Assemblies, in xxx seconds
Application.AssetDatabase Initial Refresh Start

delete the cache, restore the system cannot fix it.
run Unity with -DisableDirectoryMonitor fixed it.

I am not able to make a repro, cause it dose not happen everytime, but after I and one of my collague start using Fork, we both met the problem, others are alright. I suspect fork and Unity monitor the file changes at the same time has possibilities to make it deadlock.

I tried changing git instance settings, didn't fix it

[JeReT]

I never experienced this and worked with Unity+Fork a lot already.
Maybe you have some things in the repository that should be ignored (like Library or Temp folder)?

[DanPristupov]

Hi,

It's difficult to be precise without more information, but I'll try to give some details:

• Windows handles multiple fs watchers without a problem, and deadlocks on the system level are not possible.
• When Fork performs a background refresh it always uses --no-optional-locks to prevent writing to the .git/index file, so repository files remain untouched.

Does the hang still occur when Fork is closed?