Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2018.4
2019.4
2019.4.23f1
2020.3
2021.1
2021.2
Issue ID
1324348
Regression
No
[macOS] Crash when FileSystemWatcher is used on a large number of files
Reproduction steps:
1. Open the attached project "Case_1324348"
Reproducible with: 2018.4.35f1, 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
Notes:
- The behavior can differ depending on the number of files. Sometimes errors are thrown in the Console, sometimes the entire Editor UI breaks, sometimes the Editor opens only to cash immediately after. With enough files, the Editor always crashes as soon as you attempt to open it.
- Not reproducible on Windows
- Often crashes with this error:
"Shader compiler process initialization failed: Protocol error - failed to read magic number
Launching external process: /Applications/2021.2/Unity 2021.2.0a17_96ee4da88f82/Unity.app/Contents/Tools/UnityShaderCompiler
Launched and connected shader compiler UnityShaderCompiler after 0.00 seconds
No explicit failure code handling for error of type 22"
-
bdovaz
May 25, 2022 08:34
-
Salvador66
May 12, 2022 10:05
Any chance this fix land in 2021 Unity?
-
artem_funzy_games
Oct 29, 2021 08:11
Any chance this fix land in 2020 Unity?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a18