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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment