Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0b11
2019.3.0f4
2020.1
Issue ID
1204973
Regression
Yes
[Profiler] Current frame data not shown after selecting previous frame for the second time.
-Frame marker is not moving to the position of the current frame for the second time.
-Also, current frame data is not shown.
Steps to repro:
1. Create a new project.
2. Window > Analysis > Profiler.
3. Enter Playmode.
4. Select any frame in the CPU section.
5. Click on the Current Frame tab.
6. Repeat step 4 & Step 5.
Actual Result:
Current frame is not showing on the second time.
Expected Result:
Current frame should be shown on the second time
Reproducible in:
2020.1.0a16, 2019.3.0f4 (e5c8d37da131), 2019.3.0b11.
Working Fine in:
2019.3.0b10.
Environment:
Occurring on Windows 10 & Mac.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment