Bug description

Server crash, maybe from a deadlock or an infinite loop.
I was setting some universal pipez on a couple of Mekanism machines and an AE2 interface.

Minecraft version

1.21.1

Mod version

1.21.1-1.2.19

Mod loader and version

NeoForge 21.1.93

Steps to reproduce

The server is down, so the following is all I can recall.

• AE2 interface: provides brine (liquid) and hydrogen (chemical)
  • 1 pipe on extract with ultimate upgrade
  • fluid filtered on brine with destination set to a machine
  • chemical filtered on hydrogen with a destination set to the other machine
  • 1 pipe to receive the machine outputs (making a loop, but the extractor has destinations set)
• Meka machine 1 (separator?):
  • 1 extract pipe on front side to send chemical output (sodium?)
  • 1 pipe on left side to receive brine fluid
  • the other machine on its right, which receives the other chemical
• Meka machine 2 (chem infuser?):
  • 1 extract pipe front to send chems (hydrogen chloride?)
  • 1 pipe on its right to receive hydrogen chemical
• Meka energy cube:
  • 1 extract pipe to provide energy to the network

Expected behavior

The server didn't crash immediately. It hanged, got laggy, then shutdown.

Log files

https://gist.github.com/emperor06/807515ab345790731d3e91fb61e15a14

Screenshots

No response

Can you provide a spark profile of this happening?

I've never done one. I'll try when I'm able to reproduce it on a minimal world.

Thank you!

Ok, apparently it was a loop. I thought setting a destination would only send items/fluids to that destination, but that's not the case.

For example, if I place 1 source and 2 destination chests, then I set a filter to output to the second chest, they both receive items (in round robin); or the first one receives them in nearest mode. In fact, setting a destination doesn't seem to do anything in whitelist mode.

That created a loop where items, gazes, and fluids went out of the ME interface, then right back in, making the server lag to death.