Page 1 of 1

[2.0.55] Crash using invalid stack size input value (RuntimeError.cpp:24)

Posted: Sun Jun 29, 2025 11:23 am
by nido@foxserver.be
Inserting a character not parsable as part of a number into an inserters 'override stack size' crashes the game. The same happens when the amount in a requester chest or the number field on a decider combinator is changed to something that is not a number (e.g. the letter 't').

What did you do?
start new game, get resources to make an inserter, make an inserter, put it down,

opened an inserter, checked 'override stack size', changed the number from '1' to 't'

What happened?
The game crashes.

The factorio log recognises the game crashed, but seems unable to generate a symbolized stack trace. The last line before the crash is:
111.170 Error RuntimeError.cpp:24: Unknown variable 't' at position 0 near 't'.
(note: 't' is the character i triet to enter into the number field.)

What did you expect to happen instead?
The expected behaviour is for the input field to reject or ignore the invalid input, and the game to continue as if nothing happened.


Does it happen always, once, or sometimes?
Happens always. To reproduce, open up an inserter and change the stack size to 't'. The game will crash. (same with all the other examples, but an inserter can be crafted minutes after starting the game.


attached log i started a new game with only the space age mods enabled, grabbed some iron plates, smelted some copper, crafted an inserter, put it down, changed the stack size to 't'.

Re: [2.0.55] Crash using invalid stack size input value (RuntimeError.cpp:24)

Posted: Sun Jun 29, 2025 1:57 pm
by Rseding91
Thanks for the report. The error is that you left "log-stack-trace-on-non-critical-exception" enabled when you aren't supposed to. That, combined with something about your systems inability to generate a stack trace has crashed the game.

Simply disable that option.

Re: [2.0.55] Crash using invalid stack size input value (RuntimeError.cpp:24)

Posted: Sun Jun 29, 2025 2:57 pm
by nido@foxserver.be
You are correct. I disabled the settings and i can now type 't' in numeric fields without crashing.

I saw other posts which referenced this particular source file and this solution. Apologies I didn't realise I have turned this option on.

Should I do something to close this report?