1.0.1: root tick and checkgaps taking too long and failing

  • This section is closed. Please do bug reports over at the FTB GitHub repos.
  • FTB will be shutting down this forum by the end of July. To participate in our community discussions, please join our Discord! https://ftb.team/discord

guesswhat123212

New Member
Jul 29, 2019
4
0
0
Version:
1.0.1

What is the bug:
after exploring some more game got laggy, FTB console shows the below
Code:
[12:11:20] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 17595ms behind, skipping 351 tick(s)
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 108.768278 ms
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 114.751109 ms
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 108.549133 ms
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 163.212951 ms
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 116.691238 ms
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 136.564914 ms
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 107.727337 ms
[12:11:21] [Client thread/WARN]: Something's taking too long! 'root' took aprox 127.048935 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 112.847759 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root' took aprox 130.751425 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root' took aprox 134.144734 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 197.261369 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root' took aprox 218.90162 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root' took aprox 147.896508 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root.tick.level.entities.regular' took aprox 103.629466 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root.tick.level.entities' took aprox 103.895353 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root.tick.level' took aprox 104.329047 ms
[12:11:22] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 248.769412 ms
[12:11:23] [Client thread/WARN]: Something's taking too long! 'root' took aprox 329.640295 ms
[12:11:23] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 184.293462 ms
[12:11:23] [Client thread/WARN]: Something's taking too long! 'root' took aprox 269.769851 ms
[12:11:23] [Client thread/WARN]: Something's taking too long! 'root' took aprox 151.335792 ms
[12:11:23] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3304ms behind, skipping 66 tick(s)
[12:11:23] [Client thread/WARN]: Something's taking too long! 'root' took aprox 132.120702 ms
[12:11:23] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 106.328559 ms
[12:11:23] [Client thread/WARN]: Something's taking too long! 'root' took aprox 130.213138 ms
[12:11:24] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 105.629362 ms
[12:11:24] [Client thread/WARN]: Something's taking too long! 'root' took aprox 126.111437 ms
[12:11:24] [Client thread/WARN]: Something's taking too long! 'root' took aprox 102.326086 ms
[12:11:25] [Client thread/WARN]: Something's taking too long! 'root' took aprox 187.520497 ms
[12:11:26] [Client thread/WARN]: Something's taking too long! 'root.tick.level.chunkCache.recheckGaps' took aprox 1013.996972 ms
[12:11:26] [Client thread/INFO]: Warning: Clientside chunk ticking took 1015 ms
[12:11:26] [Client thread/WARN]: Something's taking too long! 'root.tick.level.chunkCache' took aprox 1014.955542 ms
[12:11:26] [Client thread/WARN]: Something's taking too long! 'root.tick.level' took aprox 1021.06442 ms
[12:11:26] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 1087.054084 ms
[12:11:26] [Client thread/WARN]: Something's taking too long! 'root' took aprox 1100.916964 ms
[12:11:34] [Client thread/WARN]: Something's taking too long! 'root' took aprox 123.625359 ms
[12:11:35] [Client thread/WARN]: Something's taking too long! 'root' took aprox 109.691986 ms
[12:11:35] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 100.474075 ms
[12:11:35] [Client thread/WARN]: Something's taking too long! 'root' took aprox 117.731797 ms
[12:11:35] [Client thread/WARN]: Something's taking too long! 'root' took aprox 101.166759 ms
[12:11:36] [Client thread/WARN]: Something's taking too long! 'root' took aprox 113.963028 ms

i have 6.25 gigs for MC and 1gig for permgen used memory is hovering around 60% still early game so not much set up that should cause issues, also far away from base so its unloaded. I am near a village

Mod & Version:


Paste.feed-the-beast.com log:


Can it be repeated:
do a lot of exploring.

Known Fix:
 

tofuturkey

New Member
Jul 29, 2019
34
0
0
Please update if them problem is resolved, I am also having a very similar issue! Lag started when I crafted a Crafting Station from Tinkers Construct. Deleted the Crafting Station from the world, and restarted minecraft. The intense lag and FPS loss was gone, but ever since I have experienced lag when opening inventories etc.

I also went to the Nether for the first time, and the block-lag (or tick lag, not sure which) was rather extreme. Hit F3 and saw almost constant 200+ chunk updates, and according to Journey Map (browser not up) it was generating chunks far outside my render distance.

TL;DR and guess of what the issue is: At some point (most likely due to a combination of mods) Minecraft starts trying to render and keep rendered (chunk-loaded) chunks that are outside of your specified render range. Minecraft is up right now and I see every 15 seconds a report in the console of server overload.
 

FInaldeath

New Member
Jul 29, 2019
56
0
0
TL;DR and guess of what the issue is: At some point (most likely due to a combination of mods) Minecraft starts trying to render and keep rendered (chunk-loaded) chunks that are outside of your specified render range. Minecraft is up right now and I see every 15 seconds a report in the console of server overload.


I noticed my game keeping like 30+ chunks loaded about 2k blocks away in an area of the map i've never been to. This is on a single player world so can't be another person causing it and when i visited the area to investigate i didn't see anything there that would cause it. The chunks were loaded normally like i was there according to opis and not being forceloaded.
 

CedricB

New Member
Jul 29, 2019
23
0
0
I noticed my game keeping like 30+ chunks loaded about 2k blocks away in an area of the map i've never been to. This is on a single player world so can't be another person causing it and when i visited the area to investigate i didn't see anything there that would cause it. The chunks were loaded normally like i was there according to opis and not being forceloaded.
How does one discover if chunks are being kept loaded using Opis? I'm curious if this is happening in my world.
 

FInaldeath

New Member
Jul 29, 2019
56
0
0
How does one discover if chunks are being kept loaded using Opis? I'm curious if this is happening in my world.

Open the big map and at the top right there is a filter thing which i believe by default is set to "none" (can't remember exactly since i haven't played today and the game takes far too long to load up just to check something), you just highlight it with your mouse and use the scroll wheel and it will change the filter, keep scrolling until you get to the one for loaded chunks, you will know if it is the right one when you see a bunch of green squares on the map around where you are. To clarify though, Opis is disabled by default on the launcher so if you didn't swap out Journeymap for it you won't get this ability, at least if Journeymap has this ability i don't know how to do it.

Sorry for late reply, my internet was out like all day today (stupid Comcast).
 

CedricB

New Member
Jul 29, 2019
23
0
0
Open the big map and at the top right there is a filter thing which i believe by default is set to "none" (can't remember exactly since i haven't played today and the game takes far too long to load up just to check something), you just highlight it with your mouse and use the scroll wheel and it will change the filter, keep scrolling until you get to the one for loaded chunks, you will know if it is the right one when you see a bunch of green squares on the map around where you are. To clarify though, Opis is disabled by default on the launcher so if you didn't swap out Journeymap for it you won't get this ability, at least if Journeymap has this ability i don't know how to do it.

Sorry for late reply, my internet was out like all day today (stupid Comcast).
Thank you! I'd already switched to Opis, since JourneyMap was just a bit laggier than I'd have liked, I just never knew how to change that filter... ^^; Doesn't look like I'm experiencing that problem (yet?). Just the chunks around me, and the expected spawn chunks.
 

FInaldeath

New Member
Jul 29, 2019
56
0
0
Thank you! I'd already switched to Opis, since JourneyMap was just a bit laggier than I'd have liked, I just never knew how to change that filter... ^^; Doesn't look like I'm experiencing that problem (yet?). Just the chunks around me, and the expected spawn chunks.

No problem, the map has some pretty handy features. Unfortunately the lack of beacons and some of the other features journeymap has kinda stops me from fully using it despite having better performance with it.
 

guesswhat123212

New Member
Jul 29, 2019
4
0
0
my issue is not completly fixed however it did help. I did notice the biggest problem was the number of entities being loaded. seems like they were not dropping off either. after drilling down in the debug menu the biggest problem was under "unspecified" so I have a feeling on of the mods that adds that is buggy. correct it me I am wrong but do thaumcraft nodes still talk to each other? maybe something else I don't have to explore too often and it seems to happen mostly then.