Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.8f1
Issue ID
1137290
Regression
No
[Vulkan] memory leak is present when using PostProcessLayer in an Android build
To reproduce:
1. Build and run the attached project "Android Vulkan Unity RAM Leak.zip"
2. Observe the leakage via Attached Profiler's Memory section (check screenshot attached)
Result: memory leakage causes crashing after several seconds of application being ran (check attached logcat)
Reproduced in: 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Note: project crashes upon opening on 2017.4.24f1 with stacktrace:
0x0000000140509E88 (Unity) CollectAndProduceGameObject
0x000000014050A5EE (Unity) CollectAndProduceGameObjectHierarchy
0x000000014050A9B1 (Unity) CollectAndProduceClonedIsland
0x000000014050AA6D (Unity) CloneObjectImpl
0x000000014050B236 (Unity) InstantiateObject
0x0000000140B190C8 (Unity) InstantiateObjectRemoveAllNonAnimationComponents
0x000000014135A8AB (Unity) EditorUtility_CUSTOM_INTERNAL_CALL_Internal_InstantiateRemoveAllNonAnimationComponentsSingle
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Standard Unity Materials and Shaders become corrupted after importing specific Asset Packages
- [Linux][OpenGL][Vulkan] Draw calls are not shown in the Event List when taking a capture of a frame with RenderDoc
- Inaccurate collision detections when Rigidbody Collision Detection is set to "Continuous" or "Continuous Dynamic"
- Crash on Object::IncrementPersistentDirtyIndex when upgrading project version
- [iOS] Multiple Xcode project instances created before opens up when performing Build and Run for iOS Platform
Add comment