Search Issue Tracker
Active
Votes
2
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Emissive Mesh emissiveness does not change when the Area Light intensity is animated through script
- No error notification is displayed when creating a tag with an already existing name
- Scripting API Manual Page's layout is broken when using Unity 6 manual version or above
- [Android] [iOS] Popping/crackling sound occurs when the app is repeatedly brought to the background and foreground while the sound is playing
- UI Builder unloads UXML file and discards any unsaved changes when entering Play Mode with Domain and Scene Reload enabled
Add comment