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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2020.2.X):
This cannot be supported for OOPP.