Search Issue Tracker
Fixed in 1.0.3
Votes
0
Found in [Package]
2019.3.14f1
2020.1.0b9
2020.2.0a4
2020.2.0a8
Issue ID
1248631
Regression
Yes
[Profiler] throws errors when Play Mode is paused after closing and opening Profiler window and pulling data to Profile Analyzer
How to reproduce:
1. Create and open a new project
2. Install Profile Analyzer package from the Package Manager
3. Open Profiler and Profile Analyzer windows from Windows > Analysis. Ensure that the CPU Module is enabled with the Timeline selected.
4. Enter Play Mode and make sure that Profiler is recording data
5. Press "Close Profiler Window" in the Profile Analyzer window
6. Press "Open Profiler Window" in the Profile Analyzer window
7. Press "Pull Data" in the Profile Analyzer window
8. Pause Play Mode
Expected results: no errors are thrown
Actual results: NullReferenceExcpetion and ArgumentException errors are thrown
Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.1.0b10, 2020.2.0a4, 2020.2.0a12
Not reproducible with: 2018.4.23f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a3
Notes:
-This doesn't always reproduce on the first try but after the errors are thrown once, on subsequent attempts this issue is consistent
-This issue seems to come from Profiler and not Profile Analyzer since reproduction isn't dependant on Profile Analyzer's version but rather on Editor's version
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- 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
Resolution Note (fix version 1.0.3):
Fixed in 2020.2.0b1
Resolution Note (fix version 1.0.3):
Fixed in 2020.1.5f1
Resolution Note:
Fixed in 2019.4.11f1