Search Issue Tracker
Fixed
Fixed in 2022.2.15f1, 2023.1.0b12, 2023.2.0a6
Votes
4
Found in
2021.3.11f1
2022.1.20f1
2022.2.0b10
2023.1.0a14
2023.2.0a1
Issue ID
UUM-16391
Regression
Yes
Crash on MemoryManager::Deallocate when reimporting VFX Graph Asset
Reproduction steps:
1. Open the user’s attached project
2. In the Toolbar, click CRASH > CRASH
Expected result: The VFX Graph Asset is reimported
Actual result: Unity Editor crashes
Reproducible with: 12.0.0 (2021.2.0a4), 12.1.7 (2021.3.11f1), 13.1.8 (2022.1.20f1), 14.0.3 (2022.2.0b10), 15.0.1 (2023.1.0a14)
Not reproducible with: 10.10.0 (2020.3.40f1), 11.0.0 (2021.2.0a3)
Reproducible on: Ubuntu 20.04.5, Windows 11 Pro 21H2
First lines of the stack trace:
{noformat}0x00007ff69717e02f (Unity) MemoryManager::Deallocate
0x00007ff69718748a (Unity) free_alloc_internal
0x00007ff69812836b (Unity) VFXRenderer::Clear
0x00007ff69814f118 (Unity) VisualEffect::DestroyData
0x00007ff69815be19 (Unity) VisualEffect::SetVisualEffectAsset{noformat}
Comments (3)
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
- [Android] [iOS] [UnityWebRequest] Requests with "UnityWebRequest" are open for SSL Proxying
- SetWindowsHookEx does not prevent Windows key input when Editor or Player Window is focused and Active Input Handling is set to “Input System Package (New)” or “Both”
- Crash on GetEffectiveBc7TextureCompressor() when loading and unloading all Assets in the Project
- Terrain Masks do not ignore the mipmap limit
- "Build And Run" the project for Web is allowed even though the directory for the non-default browser is not selected
Zekiel
Mar 23, 2023 09:49
In my case, I'm not removing any VFXRenderer. I have simple scene with one VFX and it crashes either when I try to edit the VFX or when I press "Play". I also tried on another computer with a new project, same issue.
I'm using the packages : entities and entities.graphics (with URP). Maybe they're not compatible with the VFX Graph?
gabriel-delacruz
Mar 19, 2023 09:15
This is currently being backported to 2022.2.
The issue occurs when you remove the VFXRenderer component while the gameobject is disabled.
Manually removing the VFXRenderer is not recommended, but if you have to do so, just make sure that the gameobject is enabled when you do, as a workaround.
Zekiel
Mar 18, 2023 10:06
I have the same issue with Unity 2022.2.11f1. Is there any workaround? I couldn't find any.