Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.7f1
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133645
Regression
No
Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
Steps to reproduce:
- Open any 2 Projects with the same Editor Version
- Open the Standalone Profiler in both Projects (Window > Analysis > Profiler (Standalone Process))
- Try switching the "Player Name" or Profiling Target to "Edit Mode" or "Play Mode" in the Profiler that was opened second
Actual results: Target is initially set to the Project from which the Profiler was opened from, Profiling Target changes to the other Project if a Standalone Profiler was launched from it in, this will last until Project is restarted and no other Profiler processes are run before. After the Target is switched to other Project, neither Play Mode or Edit Mode can be Profiled
Expected results: When switching to Edit or Play Mode target, it switches target only in that Project from which the Profiler was initially launched from, Projects are only switched when directly switching via IP
Reproducible with versions: 6000.0.67f1, 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Tested on (OS): Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment