Open 1.2.0: BC Filler hangs up server

[Yaeger]

Version:
1.2.0

What is the bug:
On a stock multiplayer server (1.3.1) a BC filler caused th server to turn unresponsive. Players could log in, but the server would be unresponsive, with the following messages:

[10:42:23] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 286416ms behind, skipping 5728 tick(s)

As soon as I managed to break the filler, everything returned to normal.

I have a copy of the world with the filler in place, and it causes the same problem on 1.2.1, 1.3.1 and 1.3.4.

Mod & Version:


Paste.feed-the-beast.com log:


Can it be repeated:
Don't know, but I will try to reproduce it on a test world in single player.

Known Fix:
Break the filler

 

[psp]

What version is Buildcraft? (too lazy to check)
The new version, 6.4.5, is supposed to fix filler/quarry lag issues.
http://www.mod-buildcraft.com/

 

[Yaeger]

Infinity 1.3.1 uses BuildCraft 6.4.3.

I tested it with Infinity 1.3.4 as well, but don't ask me which buildcraft version is in there.

Edit : 6.4.5 may be a good choice, this may definitely have been the cause:

• (Fix attempt) [#2584] Filler lag when out of blocks (asie)

 

[asiekierka]

If it persists, fire up VisualVM, double-click on your Minecraft instance (launchwrapper something), pick Sampler, click CPU, let it run for a few minutes, create a thread dump and save it and send it to me.

 

[Yaeger]

The problem is solved for now, and thanks for the tip, I will give visualVM a spin.

 

[asiekierka]

The problem is solved for now, and thanks for the tip, I will give visualVM a spin.

Did BuildCraft 6.4.5 fix it?

 

[Yaeger]

I tested it on Infinity 1.3.1, with buildcraft upgraded to 6.4.5. Sadly, that didn't fix it (or I did something wrong?). I will see if I can rerun this on my windows machine with visualVM.

 

[Yaeger]

While creating the thread dump I noticed a lot of spam on the console, several 100s of lines per second:
[18:13:28] [Client thread/INFO] [STDOUT]: [buildcraft.builders.gui.GuiFiller$FillerParameterSlot:getParameter:39]: getParameter 1 0
[18:13:28] [Client thread/INFO] [STDOUT]: [buildcraft.builders.gui.GuiFiller$FillerParameterSlot:getParameter:39]: getParameter 2 0
[18:13:28] [Client thread/INFO] [STDOUT]: [buildcraft.builders.gui.GuiFiller$FillerParameterSlot:getParameter:39]: getParameter 3 0
[18:13:28] [Client thread/INFO] [STDOUT]: [buildcraft.builders.gui.GuiFiller$FillerParameterSlot:getParameter:39]: getParameter 0 0

The filler is empty.

 

[TehTub]

I had this issue in 1.2.1. I tracked it down to a regression in WAILA (Addressed in WAILA 1.5.10) causing excessive NBT queries when looking at the filler. Try adding .disabled to the servers WAILA and WAWLA mod .jar's. Waila will still work for the most part clientside but should remove the issue from the server. At least it did for me.

 

[Yaeger]

For me this issue is closed (as I managed to remove the filler), and I can see on github that Buildcraft 6.4.6 should contain the proper fix for this issue, so I consider this closed.

 

[asiekierka]

WAILA fixed it in 1.5.8/1.5.10, WAWLA however also breaks it.

For a 100% definite fix, update BuildCraft to 6.4.6, WAILA to 1.5.10 and disable WAWLA until DarkHax releases an update (he said it will be this weekend).

Closed.