Search Issue Tracker
By Design
Votes
0
Found in
2020.1
2020.1.0b14
2020.2
Issue ID
1261033
Regression
No
[Profiler] Autoconnect Profiler build setting opens a new Profiler instance even when a standalone Profiler window is open
Reproduction steps:
1. Create a new project or open an existing one
2. Open standalone Profiler (Window -> Analysis -> Profiler (Standalone Process))
3. Open build settings (File -> Build Settings...)
4. Enable "Development Build " and "Autoconnect Profiler"
5. Build and run
Expected result: Standalone Profiler is connected to the build
Actual result: A new Profiler instance is created and connected to the build
Reproduces on: 2020.1.0f1, 2020.2.0a18
Reproduced on platforms: Android, Windows standalone
Notes:
The issue is not reproducible on Unity 2019.4 and below because standalone Profiler is not available
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
- Addressables Report window UI is broken when opening via Build > New Build > Default Build Script
- Addressables Profiles window UI break when creating a new Variable with a long name
- No character limit when renaming Profile in Addressables Profile window, allowing excessively long names
- Blurry, low quality Active Profile icon used in Addressables Profiles window
- Tree Asset Preview window is not updated after assigning a new Material
Resolution Note:
Standalone Profiler is an independent Unity instance and must have its own connection to Unity Player. This might be addressed in the future when we added multi-connection support for Unity Player debug link.