-
Bug
-
Resolution: Fixed
-
1.14.4, 19w35a, 19w44a
-
None
-
Confirmed
-
Debug
-
Low
The bug
When pressing Shift+F3, is possible to enable a profile debug diagram / pie chart that shows how much rendering time is spent on what. Using the number keys, you should be able to dig into certain causes further. Since 1.14.4, that is no longer possible.
For me, when this was the case, the following messages appeared in the game protocol:
[01:29:11] [Client thread/ERROR]: Profiler tick already started - missing endTick()? [01:29:11] [Client thread/ERROR]: Profiler tick ended before path was fully popped (remainder: 'root'). Mismatched push/pop? [...] [01:29:12] [Client thread/ERROR]: Cannot push 'mouse' to profiler if profiler tick hasn't started - missing startTick()? [01:29:12] [Client thread/ERROR]: Cannot pop from profiler if profiler tick hasn't started - missing startTick()? [01:29:12] [Client thread/ERROR]: Cannot push 'mouse' to profiler if profiler tick hasn't started - missing startTick()? [01:29:12] [Client thread/ERROR]: Cannot pop from profiler if profiler tick hasn't started - missing startTick()? [01:29:12] [Client thread/ERROR]: Cannot pop from profiler if profiler tick hasn't started - missing startTick()? [01:29:12] [Client thread/ERROR]: Cannot push 'fpslimit_wait' to profiler if profiler tick hasn't started - missing startTick()? [01:29:12] [Client thread/ERROR]: Cannot pop from profiler if profiler tick hasn't started - missing startTick()? [01:29:12] [Client thread/ERROR]: Profiler tick already ended - missing startTick()? [...]
To reproduce
- Enter a world
- Press Shift+F3
- Press 1 (for example, you can also try any other number keys)
→
The diagram will disappear and the error message appears in the game protocol
