Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
12.0
Issue ID
1346829
Regression
Yes
[VFX graph] Crash on VFXMemorySerializerBindings::StoreObjectsToByteArray
How to reproduce:
0. Set up master or vfx/staging in manifest.json
1. Open the attached project
2. Open VFX asset
3. Create Set Position(Shape:AABox) block in Initialize and convert it to subgraph Block
4. Open created Subgraph and connect AABox operator to Set Position(Shape:AABox) block
5. Expose AABox inline operator and save the subgraph
6. Double click VFX asset
7. --Observe the crash
Reproduced on: 2022.1.0a1(master)
A few lines from the stacktrace:
0x00007ff6d25a2229 (Unity) VFXMemorySerializerBindings::StoreObjectsToByteArray
0x00007ff6d0720946 (Unity) VFXMemorySerializer_CUSTOM_StoreObjectsToByteArray
0x000002a890825885 (Mono JIT Code) (wrapper managed-to-native) UnityEditor.VFX.VFXMemorySerializer:StoreObjectsToByteArray (UnityEngine.ScriptableObject[],UnityEngine.CompressionLevel)
0x000002a890825613 (Mono JIT Code) [VFXGraph.cs:363] UnityEditor.VFX.VFXGraph:Backup ()
0x000002a890825083 (Mono JIT Code) [VFXViewControllerUndo.cs:23] UnityEditor.VFX.UI.VFXGraphUndoStack:.ctor (UnityEditor.VFX.VFXGraph)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1345426