Search Issue Tracker
By Design
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.2f1
2019.2.0a1
2019.3.0a1
Issue ID
1171276
Regression
No
'Serialization depth limit 7 exceeded...' warning is thrown when declaring a private property
How to reproduce:
1. Open user's attached project and 'SampleScene' scene
2. In Console window inspect thrown warning
Expected result: no warning message is thrown
Actual result: "Serialization depth limit 7 exceeded at 'EasyBezier::BezierPoint.<TestPath>k__BackingField'. There may be an object composition cycle in one or more of your serialized classes." warning message is thrown
Reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0b10, 2019.3.0a11
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
This is by design and undocumented.
Unity serializes all serializable private fields when reloading assemblies to make it easier to make hot reloading of code in play mode work. E.g. less fields have to be updated. Private fields are not serialized in other serialization cases, such as when loading scenes.