Search Issue Tracker
Active
Under Consideration for 2022.3.X
Votes
6
Found in
2022.3.60f1
Issue ID
UUM-99968
Regression
No
Memory slowly builds up when using "Mesh.SetVertices()" function in Vulkan
How to reproduce:
1. Open the “MeshMemoryLeakIssue.zip“ project
2. Uncheck the “Auto Graphics API for Windows“ in Project Settings > Player > Other Settings
3. In the Project Settings, add the “Vulkan“ Graphics API into the Graphics API list and drag it to the top (then restart the Editor)
4. Open Edit > Build Profiles
5. Enable Development Build and Autoconnect Profiler
6. Build and run the project
7. Hold the left mouse button on the Memory module lines and observe the Profiler window
Expected result: Memory usage does not grow
Actual result: Memory usage is slowly building up
Reproducible in: 2022.3.60f1
Could not test in: 6000.0.42f1, 6000.1.0b10, 6000.2.0a6 (the Player crashes upon launch)
Reproduced on: Windows 11 Pro (24H2), Windows 11 (23H2)
Not reproduced on: No other environment tested
Notes:
- Not reproducible with DX11 and DX12
- Was unable to reproduce the issue in other projects
- Memory increase is also observable in the Task Manager
- I did not look for the fixed in version as it’s likely just an accidental fix, and the bug takes a fairly long time to reproduce after changing versions
Comments (2)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
hoshos
Sep 10, 2025 18:39
It's been six months since we reported this issue.
There's still no progress.
This is an important issue, so please don't ignore it.
hoshos
May 11, 2025 04:30
Any progress on this issue?
We're in trouble.