Search Issue Tracker
Fixed
Fixed in 6000.5.0a6
Votes
0
Found in
6000.0.65f1
6000.5.0a4
Issue ID
UUM-131071
Regression
Yes
Profiler (Standalone) window doesn’t open
Steps to reproduce:
1. Create new Unity project
2. Open Profiler (Standalone) window
3. Observe the Editor
Actual results: Profiler (Standalone) window doesn’t open
Expected results: Profiler (Standalone) window opens without any issues
Reproducible with versions: 6000.5.0a4 (35ed6e8537f8)
Not reproducible with versions: 6000.5.0a3 (d715b48dcd52)
Tested on (OS): macOS Tahoe 26.1 (M1), Ubuntu 24.04, Windows 10
Notes:
Trying to open Profiler (Standalone) window again, a warning is thrown in the Console window:
Profiler (Standalone Process) already launched. Focusing window.
UnityEditor.ProfilerWindow:ShowProfilerOOP () (at /Users/bokken/build/output/unity/unity/Modules/ProfilerEditor/ProfilerWindow/ProfilerWindow.cs:984)
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
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
Resolution Note:
Verified by CQA.
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Verified by CQA.