Search Issue Tracker
Duplicate
Votes
0
Found in
4.6.1p2
Issue ID
661511
Regression
No
Unity crashes when text serializing a field named "Base"
Steps:
1) Create a new Unity project
1a) Go to Editor settings, change Serialization Mode to "Force Text"
2) Save the scene, name it anything
3) Create a new C# file, name it "Dummy"
4) Edit Dummy.cs like this:
[System.Serializable]
class Dummy {
public string Foo;
}
5) Create a new C# file, name it "CrashUnity"
6) Edit CrashUnity.cs like this:
class CrashUnity: MonoBehaviour {
public Dummy Base; // NAME IS IMPORTANT
}
7) Create a new gameObject in the scene, name irrelevant
8) Attach CrashUnity.cs to the new gameobject
9) Click on the new gameobject and save the scene.
10) (EXPECTED) Unity does not crash. GameObject shows a "Base" field which allows one to edit "Foo".
10) (OBSERVED) Unity crashes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment