[Rseding91] [2.0.11] Stack inserter deadlocks with containers

[kj16609]

When having a mixed stack belt it is possible for the stack inserter placing items into a container such as an assembler to deadlock. The inserter is stuck attempting to pickup more items and never returns to functioning.

Broken.mp4

Video of stack inserter deadlocking

(7.83 MiB) Downloaded 245 times

This caused me a few issues when I finally upgraded to using stack inserters as portions of my base would stop functioning due to reaching this locked up state.

This state can also be reached from machines on Gleba when the items inside of them turn into spoilage, Causing the machine to not be able to output anymore if you have a single stack inserter as the only inserter and if the spoilage doesn't exactly line up to the required amount for the stack inserter to function.
It was driving me mad trying to figure out why the inserters were randomly deadlocking and most of my factory grinding to a halt.

[Rseding91]

Thanks for the report however that is working correctly. If you can not feed enough items to the stack inserter it will wait until you eventually do. If you don't want that behavior, don't use stack inserters.

[kj16609]

The thing that makes me think this is a bug is that the stack inserter will keep picking up items when going from one belt to another, Even if the belt has mixed stacks. Which is not what matches when going from a belt to an assembler.

I guess to clarify. The issue is that the stack inserter will not continue to pickup more items from the belt and insert into the assembler, Despite the status of the inserter being "Waiting for more items".

Edit: I've also renamed the topic title to be more accurate to the issue

[Rseding91]

I see now, I was looking at the wrong inserter in the video.

[kj16609]

Thanks for looking at it again. I could of probably made it a bit more obvious what the issue was, Sorry.

[robot256]

Another potentially related report of a stack inserter getting stuck when items are available: 121423

[malventano]

I see now, I was looking at the wrong inserter in the video.

Just ran into this. Here is more amplifying info in case it has not been fully reporo'd:
- Appears when assembler is feeding from both sides of a mixed belt with a stack inserter. Stack inserter will be stuck 'waiting for more items' even if there are items within reach on the belt.
- An assembler feeding from only one side of the belt seems to be ok (yellow ammo in below pic is ok).
- If I swap from bulk inserters to stack inserters feeding the grenade assemblers in the below pic, they will eventually deadlock similar to the red ammo assembler.
- I thought this had something to do with differing height stacks, but have seen it happen with a fully saturated (stacked) belt.
- I believe the hang occurs if the assembler asks for a second item in the middle of the stack inserter picking up the first.

20241124-225208-.png (2.72 MiB) Viewed 2481 times

If more is needed let me know and I can try and create a reliable repro scenario / save.

[irisfofs]

I think the inserters are stuck because the assembler is over the automated insertion limit for the item in their hand. In your screenshot, the stack inserter is holding steel, but the assembler has 15 steel, which is over the automated insertion limit for that configuration.

What confuses me is why the inserter picked up steel in the first place. Normally, inserters don't pick up items that the machine doesn't need, and it just filled the assembler to over capacity. It also stops picking up more steel (it doesn't end up with 16 in hand), so it's clearly aware the machine is over capacity, but seemingly only after it picked up the steel.

Jammed state:

12-02-2024, 13-12-13.png (224.23 KiB) Viewed 2301 times

In my testing, it seems to happen much more often (maybe only?) when the stack size on a belt varies. Even one-time switches (like going from 1 to 4 from switching to stack inserters upstream) trigger it. I suspect occasional stack size changes (from upstream non-stack inserters, construction / deconstruction, or similar) are the main cause of deadlocks in real factories.

I made a blueprint that reproduces the issue (tested with max stack size research). After belts are saturated:
- Switching the splitter input priority from left to right (increasing stack size) will jam the inserter. After removing the items stuck in hand, it works normally.
- Swapping from right to left (decreasing stack size) doesn't seem to jam it.
- Removing input priority (mixing stack sizes) will jam the inserter repeatedly.

0eNrNWd2OqzYQfhXkq1aCFRgDIVIv+gztXXUUOTBk3QOG2mbP5qzy7h1glyS7ZjdAKyXKRYLH3/x45vPYvJB92UKjhDRk+0Jy0JkSjRG1JFvye2FAOeYRnIpnj0KCow1XRjtt4zr6hzDdw0MvoJtSmE5ayKY1DgLWSpijU6i6ckoojGNqR4nDo3F+iLJEwO/QTxRSg+om/s0rp5YZPDh/tkp2uO+g6qJwfqnEczeEdmTfHS1+gv71AlCYHkZBA9xAXh4fiEtEVktNtn+9EC0Okpedn5JXgA7ugeMgOaGQzOGZbIPTN5eANMIIGOb0f4472VZ7UCjgvpvrkqbWYgjYC0EIL6EPkUuO+Ctg/kPUgRuoBjSRX2jXDUDuVXXeluCF5CyIcnIn5BPqrtVxmHj+hyb07pOtf3InRtCPE37dD/bTr+2P79n+cLQfSsiMEpkHEtTh6GEGgyp4BrYl8UeH0Mp9WxSgdl32oCZ//FjUsVGdkIWQOORlj6CNLWzxGLYwHcL2OmWnwRjM2j4yCqr6CXYtjpVoMOS716AZ1cLJYkJ09vi5UaC1ZxSXuqmV8fZQWk1hZ1M2aIoFNV6HmtpRkxG14Np4b7VtA4veRysXChe0F2EW6M2swguTe0vcdH7AE//sT2wPeOCPsL0Bn4Y8vYa7CnlAbehntuNaQ7UvMYu9170AA2fRkbzX8U/LcWc4dn43IsMpqFI0HWQjQGUdoKpbmWvEPfCfCDzK7M5zZa0qZO7JFYWiEJkAmR3nLyubXFZ2saxTI3RyJJxKhYCuK76pXAjXwSYTsGzWlnF/lRdE86iD3Z0D8TruYBMLm6yDjSZgN7dvAsn7qF8w0saGna5L8QmTqb9o34puIlEazKufu0s/StflCZ0I+hK62lzDfpkwlH1Q8nZS+axNDMPXBg4PILu3AwhidAcZYlOzpElLvw5RPKP9vKilcEH7WfBSg0uGx0PmvZUEhpir6nJ/znDHNn3v7BJMxr5BMF4JvDftfJayOrWAdi6do7dV3ZmFdLvHFO9lbfU81p3V2HTe3hHc3XnJX1e8vj0zw2AdbDABS9fV0RRsuA52KghsHYP5N2VyGK3TEtzCk+GS82D8iRK7K8kcNo6T60AN1HRZTwag9JqSm46TLIeFrK4arjgWCz79rSu4ujU3Unq4WUdTU6mYzqB09oFY/iNKz+qmATWGbg2dM3+ZQ/7CKxKrP9eZsMqdYMaBOvqkAGx3GIwuA/dvAg/n9Zl3t1WxGZdtSTg6QtM7zaRo1RZJJ67Y2EemLmue2/tZeh2jywxyiTn21zADJdookCW3q4rTSVXddcfXujaLWt1Fi/8/8OK3oUC62htfp7ik5LjO+OyP/m3F1ZsOhUK1E6DQE9rQOxfFNGVpGrGUbmLmn07/Aja6eds=

Copy blueprint

12-02-2024, 13-29-14.png (617.35 KiB) Viewed 2301 times

[Rseding91]

Thanks for the blueprint to reproduce it. I was able to figure out the issue and it's now fixed for the next release.

[malventano]

I believe this was fully resolved in .22/.23.

[Rseding91]

I believe this was fully resolved in .22/.23.

It is in “resolved for next release” which has not gone out yet.

[malventano]

I believe this was fully resolved in .22/.23.

It is in “resolved for next release” which has not gone out yet.

Understood. Seems odd though as I had a setup that appeared to be triggering this bug, and on .23 I've switched that setup back over to stack inserters and have not yet repro'd after several days.