Search Issue Tracker
Fixed in 4.5.X
Votes
0
Found in
4.1.3f3
Issue ID
546872
Regression
No
After script caused a crash in Unity, an unsaved broken prefab causes a crash
To Reproduce:
1. Open crashTest project, (attached here, but taken from case 565404)
2. Save scene
3. Place a few cubes in the scene
4. Turn one of the cubes into a prefab
5. Attach the NewBehaviourScript to the cube
6. Enter play mode, unity crashes (due to infinite loop in the script)
7. Open Unity and the project again
8. Changes to the scene are not saved, but the prefab is in the project view.
9. Rename the prefab into a fully new name
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment