Search Issue Tracker
Fixed in 0.5.0-preview.1
Votes
0
Found in [Package]
0.4.0-preview.3
Issue ID
1178710
Regression
No
Profile Analyzer cuts off a frame when saving the pulled data from the Profiler
How to reproduce:
1. Download the user attached .data file
2. Create a new project and install the Profile Analyzer package
3. Open the Window-> Analysis-> Profiler
4. Load the .data file to a Profiler
5. Open the Window-> Analysis -> Profile Analyzer
6. Click on "Pull Data"
7. Click "Save", and then load the .pdata file
8. Compare the performance of WebSocketClient.Update() method on the frame 146 in the profiler and Profile Analyzer
Expected results: Both Profile Analyzer and Profiler show the same performance data
Actual results: While Profiler shows that WebSocketClient.Update() took 1.11 ms to complete in frame 146, Profile Analyzer shows that it was on frame 145
Reproducible with: 2019.2.3f1, 2019.3.0b1, 2020.1.0a2 (package ver. preview.3 - 0.4.0; preview.6 - 0.4.0)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment