Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.2
2020.2.0a11
Issue ID
1244759
Regression
No
[Profiler] Errors are produced in Console when switching between Flow Events
How to reproduce:
1. Open user's attached "1241230_profiler" project
2. Open Profiler (Window->Analysis->Profiler)
3. Enter Play Mode
4. Select Playmode recording option and start recording data
5. Pause Play Mode
6. Turn on 'Show Flow Events' in profiler (vertical ellipsis on the top right of Module detail panel and check Show Flow Events)
7. Click on Flow Events in the captured data
8. Load in user's attached "floweventstest.data" (Top right of the Profiler window press load button)
9. Click on Flow Events in the loaded data
10. Capture data and click on Flow Events
11. Cycle between capturing data and clicking on Flow Events and loading attached data and clicking on Flow Events
Expected results: No errors are thrown in the Console
Actual results: The "ArgumentNullException" error is thrown in the Console
Reproducible with: 2020.2.0a5, 2020.2.0a11
Could not test with: 2017.4.40f1, 2018,4,22f1, 2019.3.14f1, 2020.1.0a22 because Flow Events were not introduced, 2020.1.0a23, 2020.1.0b9, 2020.2.0a4 because could not load in the data
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
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b3