extreme lag occurs in newly created world, and when opening the debug pie, you can dive infinitely in "root.root.tick.root.root.root.tick.level.root.root.root.root.tick.root" (chose always "root", or if there is no "root", then chose "tick")
you have to wait a little before "root" is showing up on the debug pie, the more you wait, the more you can dive into infinite root
This specifically happens when an entity is removed; with spawning disabled it will only get deeper if you manually create and kill an entity. However, in normal situations, entities are spawning and being removed all the time, causing it to constantly get deeper. This is specifically from the new code used to tick entities; when it returns false it fails to end the profiler section.
when debug is started you can see insanely long messages like
Something's taking too long! 'root.tick.level.entities.regular.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.root.tick.level.entities.regular.remove.root.tick.level.entities.root.root.root.root.root.root.root.root.tick.level.entities.regular.remove.remove.remove.remove.root.tick.root.tick.root.tick.level.entities.regular.root.root.tick.root.root.tick.level.entities.regular.remove.remove.root.tick.level.entities.regular.remove.remove.remove.root.root.tick.root.root.root.root.root.root.tick.level.entities.root.tick.root.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.root.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.root.tick.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.root.tick.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.root.tick.level.entities.regular.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.remove.root.gameRenderer.gui.debug' took aprox 686.731299 ms
after testing, it seems to happen only when debug screen is active, and closing debug screen stop all lags
Attachments
Comments 5
Ah, this would be an issue with something unmatched in the profiler. Workaround would be to not hold shift when opening the debug menu, as that means the profiler won't start. (If you're on a laptop, try FN+F3 instead).
Actually, I can't reproduce this in 18w31a, only 18w30b. The profiler issue seems to be gone; I'm no longer getting recursive things. If you're getting messages logged, but they're just "Something's taking too long! 'root' took aprox 142.036418 ms" and not the super deep ones, that's not a recursive issue but just a slow machine.
I'm pretty sure that this is thus fixed, but I'd like you to confirm that you're not getting recursive messages and just single-level warnings now. If you are getting recursive ones in 18w31a, can you place post your log?
Actually I'm 99% sure that this is fixed, since it seems like the fix to MC-121152 was reverted.
Can confirm.