Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.25f1
2023.2.19f1
6000.0.0b16
Issue ID
UUM-70276
Regression
No
Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
How to reproduce:
1. Open the “CrashRepro” project
2. Build And Run
Reproducible with: 2021.3.37f1, 2022.3.25f1, 2023.2.19f1, 6000.0.0b16
Reproducible on: macOS 14.4 Sonoma (Intel)
Not reproducible on: No other environment tested
Notes:
- Only reproducible in Player
- User noted that the crash occurs if the serializable struct "TestStruct" is in the System namespace. There is no crash when the struct is in another namespace or without a namespace
- User also noted that the serialization of the struct is correct when viewing the "SampleScene" file with a text editor
First few lines of the stack trace:
#0 0x0000010d4aa5e1 in operator delete[](void*, std::nothrow_t const&)
#1 0x0000010d4aae4e in operator delete[](void*, std::nothrow_t const&)
#2 0x0000010ca9cf10 in operator delete[](void*, std::nothrow_t const&)
#3 0x0000010ca9d7a5 in operator delete[](void*, std::nothrow_t const&)
#4 0x0000010cc99985 in operator delete[](void*, std::nothrow_t const&)
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
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.