[Rseding91] [2.0.12] Crash manually placing chest over ghost (construction robots): Inventory::canInsertCount()

[Brambor]

I just manually placed a steel chest over a blueprint of a steel chest. Personal robots were taking the stuff from the previous chest. I had full inventory.

I cannot reproduce it, I assume it was some tick-perfect thing with bots from base / personal robots. The traceback in dump contains

Code: Select all

C:\Users\build\AppData\Local\Temp\factorio-build-9ifPTQ\src\Entity\ConstructionRobot.cpp(300): ConstructionRobot::update

which supports my theory somewhat.

Factorio uran crash.png (2.65 MiB) Viewed 1405 times

[Rseding91]

If you do ever figure out how to reproduce it let me know. I looked at the logic but I don't see what might be going wrong.

[Brambor]

Without any info about the code, I assume it can be an old bug. I would like to see git blame in related code to see, if it changed with 2.0. If not, I don't think I will encounter the bug for another 1000 hours on that version of the game.

If I had more frequent autosave I would ask you to build the chest in every tick. But I built and destroyed belts and a chest which introduces too much noise. Shame. Maybe even then it is threading specific and it would have to be rerun thousands of times for the bug to manifest.

Maybe the unlock in the construction bots can be locked for longer by adding a sleep().

But maybe you thought of all these things already .

On the one in milion chances, I will let you know!

[busata]

I've had a similar issue and situation in 2.0.15. See attached logs. Marked a lot of buildings for deconstruction (mix of recyclers/EM plants) in fulgora, logistic bots ran out of logistic storage, I placed extra yellow storage chests, they filled those too. Had yellow chest ghost blueprints (but no construction bots or chests available anymore), the moment I clicked steel chest from inventory and tried to place it somewhere (it happened fast so not sure where I placed it), it crashed.

[Loewchen]

Ref.: 121537 122241

[Rseding91]

I was able to figure out what was causing this and it's now fixed for the next release.