Search Issue Tracker
Fixed
Fixed in 6000.1.0b15, 6000.2.0a9
Votes
0
Found in
6000.1.0b5
6000.2.0a2
Issue ID
UUM-96371
Regression
No
[BRv4] The "What is the problem related to?" Field is not read-only when the new Bug Reporter is opened when the Editor crashes
Steps to reproduce:
- Open any Project and attach a script to crash the Editor
"using UnityEngine.Diagnostics
Utils.ForceCrash(ForcedCrashCategory.Abort);"
- Enter Play Mode
- Click the "What is the problem related to?" field
Actual results: Field can be edited
Expected results: Field is read-only when the Editor crashes and BR pop up
Reproducible with versions: 6000.1.0b5, 6000.2.0a2
Not reproducible with versions: 2022.3.57f1, 6000.0.37f1 (Old bug reporter)
Tested on (OS): Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment