Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.1
2020.1.0b7
2020.2
Issue ID
1243225
Regression
No
[OOPP] Standalone Profiler records Editor performance when it's switched to monitor the Play Mode
How to reproduce:
1. Create a new project with the default 3D template
2. Open Window->Analysis->Profiler (Standalone process)
3. In the Profiler Window, switch to Editor performance monitoring
4. Record the Editor's performance for a while (5-10 seconds)
5. Switch to the Play Mode performance monitoring
6. Disable recording
7. Enable recording
8. Switch between the Editor and Profiler process
Expected result: Performance is not recorded
Actual result: Editor performance is being recorded
Reproducible with: 2020.1.0b9, 2020.2.0a11
Couldn't test with: 2017.4.40f1, 2018.4.23f1, 2019.3.14f1 (Profiler Standalone Process doesn't exist)
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
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note (2020.2.X):
This cannot be supported for OOPP.