MC-139819Profiler error "Cannot push to profiler if profiler tick hasn't started - missing startTick()?"
Attachments1
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
Created Issue:
Profiler error "Cannot push to profiler if profiler tick hasn't started - missing startTick()?"
Added Affects Versions: 18w46a
Added Affects Versions: 18w49a
Added Attachments:
![[Mod] Sonicwave](../../../data/avatars/users/94627.png){kind=small}
Added Affects Versions: 19w03c
Added Affects Versions: 19w04b
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
Added Assignee: ![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg)
[Mojang] Bartosz Bok
[Mojang] Bartosz Bok
I can confirm that this issue still occurs in 18w50a:
Present in 19w03c.
Yet, a profile dump is given, but:
Time span: 3646 ms Tick span: 65 ticks // This is approximately 0.02 ticks per second. It should be 20 ticks per secondThis result is not right. The result should be 17.83 ticks per second.
It always says 0.02 ticks.
The count in the profile dump report is miscalculated in the report, but is correctly displayed as a command output.
This error is not produced when no player is on, or when all the players are in spectator mode (but the count in the report is still miscalculated). Once you switch from spectator to another game mode while the profiler is running, the error messages appear and start spamming the console until you switch back to spectator mode again.
Can confirm in 1.17
@aceplante, if you can still reproduce this in the latest release or snapshot please search for existing open reports, and in case you don't find any create a new report (and refer to this one here).