Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Votes
0
Found in
2021.1.0a1
2021.1.0a8
Issue ID
1295637
Regression
Yes
Project fails to open with the command line argument "-profiler-enable" and crash logo appears
The project fails to open on adding command -profiler-enable for project advanced settings in HUB and the Unity Crash Logo appears. The Editor.log file shows the correct command-line arguments.
Refer to the attached Video.
Steps to Reproduce:
1. Create a New Project and close the Editor
2. HUB > Advanced Project Settings > Type -profiler-enable > Click Done
3. Open the Project
Actual Result:
Project does not open and Unity Crash Logo Appears
Expected Results:
Project should open with profiler enabled
Occurring on:
2021.1.0a8, 2021.1.0a1
Working Fine on:
2020.2.0b14, 2020.1.15f1
Note: The Editor doesn't open up or crash and neither is a crash log generated.
Environment:
Windows 10 and macOS 10.15
License type: Pro
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.35f1