Search Issue Tracker
Fixed in 1.0.0
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1230000
Regression
No
[Profile Analyzer] Profiler tries to show frames that it does not have resulting in No Data Found and uninformative warning
How to reproduce:
1. Open attached project "ProfilerAnalyzerFrameSelect.zip"
2. Open Profiler window
3. Enter Play mode (to gather some data in the profiler)
4. Open Profile Analyzer window
5. In Profile Analyzer, press "Pull Data"
6. Enter Play mode (to gather some additional data in the profiler, wait for at least a few seconds so the initial frames of Profiler window are not visible anymore)
7. In Profile Analyzer, press on any Frame Link button
8. Observe Profiler and Console window
Expected result: profiler does not get empty and remains with the data it had before, an informative warning is thrown
Actual result: profiler tries to show a frame that it does not have and starts to show No Data Found, an uninformative warning is thrown
Reproducible with: 2018.4.20f1, 2019.3.6f1, 2020.1.0b3, 2020.2.0a4 (0.4.0-prev.5, 0.6.0-prev.1)
Could not test with: 2017.4 (due to errors in the console window)
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.0):
Profiler no longer tries to show non existing frames