Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.11f1
6000.4.0f1
6000.5.0a9
6000.6.0a1
Issue ID
UUM-137642
Regression
Yes
Frame Debugger window flickers when there are multiple Game View windows open
Steps to reproduce:
- Open the attached project
- Enable Frame Debugger
- Resize the Frame Debugger window
- Observe the Frame Debugger's output while resizing the window
Actual results: Frame Debugger's output keeps flickering
Expected results: Frame Debugger's output does not flicker
Reproducible with versions: 6000.3.0a3, 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1
Not reproducible with versions: 6000.0.71f1, 6000.3.0a2
Tested on (OS): Windows 11, macOS 26.3.1
Notes:
- Flickering occurs on its own, resizing the window only allows for a consistent reproduction
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
- 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
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 (6000.6.X):
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.