Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Won't Fix in 2023.2.X
Votes
4
Found in
2021.3.20f1
2022.2.9f1
2023.1.0b6
2023.2.0a4
2023.3.0a3
6000.0.0b11
Issue ID
UUM-29294
Regression
No
Editor slows down on each subsequent run when using compute shaders
Reproduction steps:
1. Open the attached “Repro.zip” project
2. Open the “Assets/Tutorial01.unity” Scene
3. Enter the Play Mode
4. Observe the FPS in the Game View’s Status window
5. Exit the Play Mode
6. Repeat the 3-5 steps
Expected result: Performance always stays the same
Actual result: Significant performance decrease each subsequent time the Play Mode is entered
Reproducible with: 2021.3.20f1, 2022.2.9f1, 2023.1.0b6, 2023.2.0a4
Couldn’t test with: 2020.3.45f1 (Errors in the Scripts due to missing/changed features)
Reproducible on: M1 macOS 13.1, Windows 10 (21H2)
Note: The issue is reproducible on both Intel and Apple Silicon Editors on M1 Mac
-
Sulfield
Mar 27, 2023 12:52
Is there by any chance an estimate when you're going to look into this issue / whether it's addressable in the short term? We'll need to plan our roadmap accordingly and also estimate how to deal with the current situation, which is quite limiting.
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.