Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.63f1
6000.0.51f1
6000.1.7f1
6000.2.0b5
Issue ID
UUM-108964
Regression
No
[Linux] FPS limit statistics in GameView becomes unreliable for some time when a context menu is open while in Play Mode
Reproduction steps:
1. Open the attached “LinuxGpuTest.zip” project
2. Open the “Assets/_LinuxGpuTest/SceneEmpty.unity” scene
3. Enter the Play Mode
4. Open Stats for the Game View
5. Set the FPS limit in-game
6. Observe that FPS is limited
7. Right-click on the “Game” tab, click “Maximize” (don't double click the tab!) Or right click in the hierarchy view to open a context menu then close it.
8. Observe that the FPS becomes unlimited and then comes down to the previously set FPS limit
Expected results: Play Mode FPS is still limited
Actual results: Play Mode FPS takes a while to return the previously set FPS limit (~10 sec when maximizing, ~30 sec when minimizing)
Reproduced with: 2022.3.63f1, 2023.3.0b1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5
Not reproduced with: 2023.3.0a2, 2023.3.0a19
Reproduced on: Ubuntu 24.04
Not reproduced on: Windows 11
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
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.