[2.0.70]Application Hang/Not Responding when placing rails

[c_str]

When placing rails in some locations causes the Factorio application to stop responding, and has to be closed via Not responding dialog box. The green rail in the attached image is one that causes the game to stop responding.

10-14-2025, 10-43-47.png (5.12 MiB) Viewed 2557 times

Windows Event Log has the following:
The program factorio.exe version 2.0.70.18650 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

I've attached the Log file though it does not show any errors.

[Loewchen]

Post the save and exact steps to reproduce this please, see 52433.

[c_str]

Steps
Place a rail in the location provided in the screen shoot
Application stops responding.


Note: Placing the rail in that column will cause the game to stop responding for a couple of chunks up. I have not tired to see how far down the error happens.

Save file is attached

[Rseding91]

I have not been able to reproduce any issue. Does the issue persist if you restart your computer? I noticed in the log file you are quite low on free RAM before the game has even reached the main menu, or loaded any save file.

[c_str]

Yes, I have tried restarting my computer that did not fix the issue.

[c_str]

I've tested the issue on a computer with more ram and it still stops responding when the Track is placed.

here is a new save with steps to reproduce

Either Place Track piece below ghost rail piece
Turn on personal roboport and wait for robot to try and place the rail.

Effect your character is unable to move, and the application stops responding.

[Rseding91]

Like this?

[Rseding91]

I seem to be missing some key part in how to reproduce the issue.

Could you reproduce it, and before it's killed - open task manager, right click on the factorio process and click "create dump". Then zip that and upload it somewhere that I can download it? It will be quite large even after zipping so it likely won't be attachable to the forums. You'll have to use something like google drive, one drive, dropbox and so on.

[Loewchen]

I am actually able to reproduce this with a non SA install and no mods.

[c_str]

Here is the zip of the dump file
[link removed]

I am actually able to reproduce this with a non SA install and no mods.

Thanks, I do not have SA installed.

[Rseding91]

It looks like this only happens in the non-space-age zip or installer version of the game and only in 2.0.70. 2.0.69 it works fine, and all other versions of 2.0.70 it works fine.

But so far I don't know why. I suspect some kind of compiler error, but that's just a guess at the moment.

[Sanqui]

It appears that the binary has suffered from some form of corruption during the deploy process, but so far we've been unable to determine the root cause. It may be a compiler bug, a hardware issue, or a bit flip caused by a cosmic ray. The build server does have ECC RAM and reported no issues so far... We will continue investigating, but since we'd like to have a version without crashes out we're also releasing 2.0.71 where this issue is rather unlikely to manifest again.

[c_str]

It appears that the binary has suffered from some form of corruption during the deploy process, but so far we've been unable to determine the root cause. It may be a compiler bug, a hardware issue, or a bit flip caused by a cosmic ray. The build server does have ECC RAM and reported no issues so far... We will continue investigating, but since we'd like to have a version without crashes out we're also releasing 2.0.71 where this issue is rather unlikely to manifest again.

Thanks I can confirm that issue is no longer happening.