Search Issue Tracker
Fixed in 1.0.4
Votes
0
Found in [Package]
1.0.3
Issue ID
1281874
Regression
No
Profile Analyzer cuts off a frame when pulling data from the Profiler
How to reproduce:
1. Open the attached '1281874.zip' project'
2. Open the Profiler (Window > Analysis > Profiler)
3. In the 'Target Selection' dropdown select 'Editor'
4. Capture data into the Profiler (exceed more than 300 frames)
5. Select the first captured frame in the Frame chart
6. Open the Profile Analyzer (Window > Analysis > Profile Analyzer)
7. In the Profile Analyzer window select 'Pull Data'
8. Compare the Frame range in the Profiler and in the Profile Analyzer
Expected result: The Frame Range in the Profile Analyzer is equal to the Frame Range captured in the Profiler
Actual result: The Frame Range in the Profile Analyzer is missing one frame
Reproducible with: Profile Analyzer 0.5.0-preview.1, 1.0.3 (2018.4.28f1, 2019.4.12f1, 2020.1.8f1, 2020.2.0b6)
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
Add comment