Search Issue Tracker
Fixed in 2019.4.X
Recursive Serialization is not supported error when calling Resources.LoadAll from static method
1. Download and open the attached "Dwarf Mountain New.zip" project.
2. Enter Play mode.
3. Notice the console.
Expected result: No "Recursive Serialization is not supported" errors are thrown.
Actual result: Few "Recursive Serialization is not supported" errors are thrown and Play mode gets paused.
Reproduced with: 2017.3.0b3, 2017.2.0f3, 2017.1.1p4, 5.6.3p4, 5.6.0f2
Not reproduced with: 5.6.0f1, 5.5.4p5, 2019.4.33f1, 2020.3.24f1, 2021.2.5f1, 2022.1.0a16
Regression introduced in: 5.6.0f2
Notes: Serialization errors appear only after the first time the game is launched. It might also appear every time game mode is entered, but if it does not, hen Unity needs to be restarted to reproduce the issue again. If in MainBase.cs script 23 lines with "singleton.InitializeProgram()" is removed, the issue does not appear since it stops all the consequent Resources.LoadAll() calls.
Error: "Recursive Serialization is not supported. You can't dereference a PPtr while loading. (Constructors of C# classes may not load objects either. See stack trace.)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Lightmaps are baked incorrectly for GameObjects when their Position is <=-2048 or >=2048 on any of the coordinates
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached