Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X
Votes
0
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1249581
Regression
No
Profiler keeps recording data when Target Selection is set to 'Editor' and the Profiler window is closed
How to reproduce:
1. Create a new project
2. Open the Profiler window (Window -> Analysis -> Profiler)
3. Disable the Profiler recording
4. Set the Profiler Target Selection to 'Editor'
5. Enter the Play Mode
6. Enable the Profiler recording
7. Close the Profiler window
8. Exit Play Mode
9. After some time reopen the Profiler window
Expected result: data recording stopped when the Play Mode was exited
Actual result: data recording continued even after exiting Play Mode with the Profiler window being closed
Reproducible with: 2018.4.23f1, 2019.3.15f1, 2020.1.0b10, 2020.2.0a12
Notes:
1. While not in Play Mode, the recording is stopped after closing the Profiler window when the Target Selection is set to 'Editor'
2. The recording is stopped after closing the Profiler window and exiting Play Mode when the Target Selection is set to 'Playmode'
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
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
Resolution Note (fix version 2020.2):
Fixed a situation when Profiler remains active even with Profiler window closed in play mode.
Fixed in 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.1f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.17f1