Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.2.1f1
Issue ID
1382078
Regression
No
NativeTests fail when running Editor through Command Prompt
How to reproduce:
1. Open the Command Prompt
2. Navigate in the Command Prompt to the Unity Editor folder containing "Unity.exe"
3. Run command "start Unity.exe -runNativeTests ExternalProcess.CanCaptureStandardStreams"
4. In the Search Bar write "%localappdata%"
5. Navigate to the "Local/Unity/Editor" folder
6. Open the "Editor.log" file
Expected result: Successful run, Unity Hub is opened
Actual result: A crash is logged
Reproducible with: 2019.4.33f1, 2020.2.0a21, 2020.3.24f1
Not reproducible with: 2021.1.0a1, 2021.2.5f1, 2022.1.0b1
Note:
- 2021.2/staging is reproducible
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a8
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b13
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.18f1