Search Issue Tracker
Won't Fix
Under Consideration for 6000.0.X
Votes
9
Found in
2021.3.28f1
2022.3.5f1
2023.3.0a1
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-44015
Regression
No
BufferMetal::AllocNewVersionedBuffer takes longer than expected
SkinnedMeshRenderer creates Metal buffers every frame, taking a considerable amount of frame time.
Issue reported by user in forum: [https://forum.unity.com/threads/unity-creates-metal-buffers-used-inside-the-skinnedmeshrenderer-every-frame-on-ios.1463129/]
Steps:
1. Open TestMetalBuffer in Unity
2. Make a MacOS / iOS build
3. Use XCode Instruments to profile
Expected: BufferMetal::AllocNewVersionedBuffer has little impact on performance
Actual: BufferMetal::AllocNewVersionedBuffer has big impact on performance
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
- [RenderGraph] Outputs from camera stack override each other when using OpenGLES3 with a custom renderer feature
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
- MeshCollider preview gizmo disappears from the Scene view when overriding the mesh asset using any 3D editing tool
- Tutorial project is not created when started from the Get set up tab
- Audio Listener Component expands when selected
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.
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.