Page 1 of 1

[2.0.77] Crash sitting in Spidertron (WakeUpList.cpp (118): alarm)

Posted: Mon Aug 31, 2026 8:07 pm
by Sauron654
What did you do?
Nothing particular. I don't think I even moved the mouse. Just sitting in Spidertron

What happened?
Game Crashed with info modal to post it here.

What did you expect to happen instead? It might be obvious to you, but do it anyway!
Game not crashing

Does it happen always, once, or sometimes?
I don't think it ever crashed before that.

Savegame: https://drive.google.com/file/d/1Kevj1W ... sp=sharing
Logs: https://drive.google.com/file/d/17X1K7p ... sp=sharing

Re: [2.0.77] Kubuntu Random Crash while sitting in Spidertron

Posted: Mon Aug 31, 2026 8:13 pm
by Sauron654
PS: AI means it saved _autosave2 so here it is if you need it:

https://drive.google.com/file/d/1IBXbEH ... sp=sharing

Re: [2.0.77] Crash sitting in Spidertron (WakeUpList.cpp (118): alarm)

Posted: Tue Sep 01, 2026 6:58 pm
by Rseding91
Thanks for the report however I don't believe there's anything we can do with this. The crash is within the transport belt logic that's alarming inserters after belts move items. Given that logic runs virtually every tick for every game that has belts if there was some actual engine bug it seems likely there would be a significant amount of crashes being reported.

More likely is you have failing or failed hardware (likley RAM), or possibly a bad RAM/CPU overclock.

That is, unless you know of a reliable way to reproduce this crash.

Re: [2.0.77] Crash sitting in Spidertron (WakeUpList.cpp (118): alarm)

Posted: Wed Sep 02, 2026 3:59 pm
by Sauron654
I would need a second job to finance new RAM but its ok for me if you leave it as is.
If you see a high number of crashes then you can investigate.

:)

Re: [2.0.77] Crash sitting in Spidertron (WakeUpList.cpp (118): alarm)

Posted: Wed Sep 02, 2026 4:43 pm
by pioruns
Sauron654 wrote: Wed Sep 02, 2026 3:59 pm I would need a second job to finance new RAM but its ok for me if you leave it as is.
If you see a high number of crashes then you can investigate.

:)
They won't be investigating something which runs on every tick, on every gamer machine, and only fail on yours. There is nothing else to investigate.
However, on your end:
Without diagnosing your hardware and replacing it, you are risking data integrity, like for example your latest Factorio save, which may fail to load next time you launch the game. Seen that many times here on the forum. Some people never save the game (still no idea how is that possible), and with 10 failed Autosaves, they loose everything.