Search Issue Tracker
Fixed
Fixed in 2022.2.X, 2022.2.0a14
Votes
0
Found in
2022.2.0a13
Issue ID
UUM-30234
Regression
Yes
Warnings are constantly generated when the Editor and Game view are on different screens
Reproduction steps:
1. Open the attached project “ALLOC_spam”
2. Position Editor and Game view so they would ve on different displays
2. Open “Assets/Scenes/01_Scene_RTX_Brett_Crashed.unity”
Expected result: No warnings in the Console window
Actual result: Console is spammed with warnings “Calling Deallocate on pointer, that can not be deallocated by allocator ALLOC_TEMP_UnityGfxDeviceWorker”
Reproducible with: 2022.2.0a12, 2022.2.0a13
Not reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.0a11, 2023.1.0b7, 2023.2.0a6
Fixed in: 2022.2.0a14
Reproducible on: Windows 10
Note: When the Game view is located on the same screen as Editor, clicking in the Scene view generates a warning
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment