Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.1p4
Issue ID
884245
Regression
No
Unity crashes on mono_custom_attrs_from_class when an incompatible script is in a prefab and one tries to apply some changes
How to reproduce:
1. Open the attached project
2. Open a new scene
3. Find NavigationPoint prefab in the project and drag it to the scene
4. Notice that it has incompatible script
5. Click the prefab Apply button
Result: Fatal Error appears "The file 'MemoryStream' is corrupted!..." and Unity crashes
Reproducible: 5.5.0b9, 5.5.2f1, 5.6.0b10
Not able to reproduce with 5.4.4p4, project crashes because of forward incompatibility. Also it is full of compilation errors
Duplicate of the WON'T FIX case:
The cause of the error is that the users project is not setup correctly, the user has added scripts that derive from ScriptableObject instead of MonoBehaviour to GameObjects, resulting in crashes.. Developer added error to detect this case, so the users can fix the issue themselves.
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
This is a duplicate of issue #886110