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
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
- Crash on mono_array_length when building a project
- "StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
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.