Search Issue Tracker
Fixed
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a1
2019.3.0b6
2020.1.0a1
Issue ID
1189854
Regression
Yes
Secondary Unity instance writes EditorInstance.json when starting the Editor
Steps to reproduce:
1. Create an empty unity project.
2. Create Material in Assets folder - This will spawn the worker process once you have enabled the OnDemand feature
3. Add an "adb2.txt" file in the unity project root
4. Put the line "OnDemand=Lazy" in it
5. Stop the editor, delete the Library folder and start the editor again.
Expected: Only the master process writes to the "Library/EditorInstance.json" file
Actual: There are a couple of Unity workers (Unity.exe) writing to the "Library/EditorInstance.json" file
Reproduced in: 2019.3.0a1, 2020.1.0a1, 2020.1.0a8
Not reproduced in: 2017.4.33f1, 2018.4.11f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS][iOS][IL2CPP] Crash when using the nullable enum as a parameter and passing a default value into it.
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
Add comment