Search Issue Tracker
Fixed in 0.2.0-preview.13
Votes
24
Found in [Package]
preview 0.1.0 - preview - 0.1.1
Issue ID
1177449
Regression
Yes
Memory leak occurs when filling NativeArray from NativeQueue since allocations are never deallocated
How to reproduce:
1. Open attached project
2. Open Profiler window
3. Enter the Play Mode
4. Select Memory part of the Profiler
5. Choose a Detailed profiling, and press Gather object references
6. Press Take a Sample Playmode and repeat after few seconds, and notice that NativeArray is leaking memory
Reproducible with: 2019.1.0a1, 2019.1.14f1, 2019.2.7f2, 2019.3.0b3, 2020.1.0a5
Not reproducible with: 2017.4.32f1, 2018.4.10f1
Reproducible with package: Collections preview 0.1.0 and up
Not reproducible with package: Collections preview.20 - 0.0.9 and down
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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
hongquang1799
Feb 01, 2020 15:24
this bug was fixed in preview 0.2.4
francois85
Jan 24, 2020 08:35
You have my vote
arkano22
Jan 24, 2020 08:25
Been experiencing this myself, *very* frustrating. Here's a bit more insight about the cause:
https://forum.unity.com/threads/memory-leak-in-nativequeue.814668/#post-5400846
yongheekim
Dec 19, 2019 09:37
I know you guys have lots of things on the plate. But I'm really frustrated by this... Because I don't have whole lot of experience with garbage collection and memory management. So It's hard to for me to pin down the cause of memory leak and fix my code... ；д；