Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0b1
Issue ID
1098279
Regression
Yes
Profiler TimelineView does not allow expanding of threads to their full depth on a loaded profiler capture
Steps to reproduce:
1. Create a new project
2. Add TestSampleGenerator.cs to the project (or any script that grantees a callstack deeper than 6)
3. Add TestSampleGenerator Component to an object in the scene
4. Deep profile the scene
5. Open the CPU Profilers Timeline view
6. Check that the main thread can be expanded far enough to see the sample "Tip()"
7. Save the profile to file.
8. Load the saved profile.
Expected Result: the main thread can still be expanded to see the "Tip()" sample
Actual Result: the main thread can not be expanded to see the "Tip()" sample
Reproduced on 2018.3.0b1, 2018.3.0b4
Not reproduced on 2018.3.0a11, 2018.2.14f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment