Search Issue Tracker
Won't Fix
Won't Fix in 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
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
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.5.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.