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
- Prefab's scripts are constantly reloaded when trying to enter multiple digits or characters into public fields on custom scripts consecutively
- Crash on mono_g_hash_table_find_slot when entering Play Mode
- [iOS] Crash when pressing "Done" on the keyboard layout
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.35f1