Search Issue Tracker
Fixed
Fixed in 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Votes
0
Found in
6000.3.0f1
6000.4.0a2
6000.5.0a2
Issue ID
UUM-128921
Regression
Yes
Maximising Frame Debugger window forces target process to Editor
Steps to reproduce:
- Open the attached project
- Open Frame Debugger window (Window -> Analysis -> Frame Debugger)
- Build and launch a Standalone build with Development mode enabled (Attached project already contains a ready macOS build)
- In the Frame Debugger window, set the Target process to the standalone build
- Enable Frame Debugging to gather data
- Double-click on the Frame Debugger window or use the Right-Click menu to maximise the window
- Observe the Frame Debugger window
Actual results: Frame Debugger's target process is forced to Editor, and the data disappears after the window is maximised
Expected results: Target process remains set to the standalone build, and data persists after maximising the Frame Debugger window
Reproducible with versions: 6000.3.0a1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2
Not reproducible with versions: 6000.0.63f1, 6000.2.14f1
Tested on (OS): macOS 26.1, Ubuntu 24.04
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note:
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1