Factorio Forums

So I've noticed that factorio likes to crash my PC (completely nonresponsive) when auto-saving on linux (no time loss saving is activated)
I have not yet noticed this behavior while manual saving.

My PC is an IdeaPad C340
CPU: Intel Core i5-8265U
GPU: Intel WhiskeyLake-U GT2 [UHD Graphics 620]

In the attachements is the corrupted auto-save which caused the crash


If you need anything more, please let me know.

If the system is crashing then there is something wrong with the system.

Well I'm a fresh windows refuge who is quite new new to linux.

If it's something wrong with the system, then how do I find out what that "something" is?

Check out 114778, the os event log might also give insight.

Please share dmesg.txt generated by this command run in terminal Maybe it will indicate why system is getting unresponsive when trying to save a file?

Also do a full pass in Memtest86+ for a good measure, to start stability checks of your computer.

I've moved from linux mint to ubuntu.

I thought that fixed it, but during my playsession today, it reappeared, but it behaved slightly differently.

Firstly, it did happen only after a substantial amount of time passed and secondly, the system forcefully closed factorio with the SIGTERM command, after which the system recovered.


I'll throw a memtest in there, but I doubt it'll find anything more (which is nothing) than the tests I've ran in between OS switch.
In the attachments I've thrown the logs and the corrupted autosave (_autosave2), which caused the crash + the autosave (_autosave1) just before the failed autosave.

Hopefully the issue can be finally be found and resolved

pioruns wrote: Sun Mar 09, 2025 9:52 am Please share dmesg.txt generated by this command run in terminal

Code: Select all

sudo dmesg >dmesg.txt

Maybe it will indicate why system is getting unresponsive when trying to save a file?

Also do a full pass in Memtest86+ for a good measure, to start stability checks of your computer.

As expected, memtest did not show me anything.

Can you share dmesg.txt from the time when you had factorio forcibly closed with SIGTERM?
How did you figure out it was SIGTERM?

I think the relevant dmesg.txt file was already overwritten :-/

And I just found out that I cannot post the dmesg...

When I try it returns:

Error

Invalid file extension: dmesg



And I figured that it was SIGTERM by reading the factorio-current.log, which I posted previously.

You have restarted your computer since Factorio crash? If your computer operates normally, you don't need to do that. Sleep/suspend on Linux works well. I only restart my laptop when there is a kernel update. In between, laptop is sleeping, for months.

You can capture dmesg log using the command I shared earlier: Created .txt file you can open with any text editor and upload to pastebin and so on. If you are trying to upload it here without extension, then I am not surprised forum does not accept it. Either give it extension or upload to pastebin.

Normally, dmesg saves information about crashing processes, so it may leave some information there, if you are able to reproduce the error again.
What about your memory usage, do you have free RAM during gameplay?

I had to restart the PC to run memtest...
And yes, my notebook is shut down when not in use.


Now I know.


Hope I can reproduce the crash...

Sserious issues are incredible rare with Wube,
so I might have discovered a unicorn lol

pioruns wrote: Fri Mar 14, 2025 6:15 pm You have restarted your computer since Factorio crash? If your computer operates normally, you don't need to do that. Sleep/suspend on Linux works well. I only restart my laptop when there is a kernel update. In between, laptop is sleeping, for months.

You can capture dmesg log using the command I shared earlier:

Code: Select all

sudo dmesg >dmesg.txt

Created .txt file you can open with any text editor and upload to pastebin and so on. If you are trying to upload it here without extension, then I am not surprised forum does not accept it. Either give it extension or upload to pastebin.

Normally, dmesg saves information about crashing processes, so it may leave some information there, if you are able to reproduce the error again.
What about your memory usage, do you have free RAM during gameplay?

Factorio needs remarkable little RAM.

My poor PC has only 8 Gigs of RAM and I still have ~1.8GB left over

Legendendear wrote: Fri Mar 14, 2025 6:31 pm Hope I can reproduce the crash...

Sserious issues are incredible rare with Wube,
so I might have discovered a unicorn lol

Yes it is very rare to get any crash at all with Factorio. Maybe that's why your bug report already has been moved to Bug Reports -> 1/0 Magic section. Even if you discovered a unicorn bug, it's probably related to faulty hardware, or other software (Linux kernel, GPU driver, and so on). Most likely this is not Factorio's fault, because your system is freezing completely, indicating a problem with I/O, not Factorio. That's why it's important to monitor dmesg log, which outputs any problems with hardware or software.
To give you perspective, I have not experienced any crash or bug since I started playing Factorio before Space Age DLC. Probably clocked 500 or maybe a 1000 hours already. Playing on Linux with native client.
Please share relevant info once you have more knowledge about your bug and how to reproduce it. Good luck!

Oh and there was another difference with ubuntu compared with linux mint.

The mouse and keyboard remained responsive.

Legendendear wrote: Fri Mar 14, 2025 6:37 pm Factorio needs remarkable little RAM.

My poor PC has only 8 Gigs of RAM and I still have ~1.8GB left over

3345.016 Info AppManager.cpp:303: Saving to _autosave2 (non-blocking).
3345.230 Info AsyncScenarioSaver.cpp:177: Saving process PID: 44684
3359.211 [44684] Received SIGTERM, shutting down

Non-blocking saving can potentially double the RAM consumption of Factorio. I think you're running out of RAM and the OS is hanging/killing Factorio as a result. I would recommend to turn off non-blocking saving.

That was my thought, about RAM.
OP, you can also try adding swap memory to your 8GB laptop, to mitigate this. Or disable non-blocking saving as Bilka suggested.

Bilka wrote: Sat Mar 15, 2025 10:52 am

Legendendear wrote: Fri Mar 14, 2025 6:37 pm Factorio needs remarkable little RAM.

My poor PC has only 8 Gigs of RAM and I still have ~1.8GB left over

3345.016 Info AppManager.cpp:303: Saving to _autosave2 (non-blocking).
3345.230 Info AsyncScenarioSaver.cpp:177: Saving process PID: 44684
3359.211 [44684] Received SIGTERM, shutting down

Non-blocking saving can potentially double the RAM consumption of Factorio. I think you're running out of RAM and the OS is hanging/killing Factorio as a result. I would recommend to turn off non-blocking saving.

Are there settings I can change to minimize RAM usage instead?

Legendendear wrote: Sun Mar 16, 2025 4:08 pm

Bilka wrote: Sat Mar 15, 2025 10:52 am

Legendendear wrote: Fri Mar 14, 2025 6:37 pm Factorio needs remarkable little RAM.

My poor PC has only 8 Gigs of RAM and I still have ~1.8GB left over

3345.016 Info AppManager.cpp:303: Saving to _autosave2 (non-blocking).
3345.230 Info AsyncScenarioSaver.cpp:177: Saving process PID: 44684
3359.211 [44684] Received SIGTERM, shutting down

Non-blocking saving can potentially double the RAM consumption of Factorio. I think you're running out of RAM and the OS is hanging/killing Factorio as a result. I would recommend to turn off non-blocking saving.

Are there settings I can change to minimize RAM usage instead?

Probably not much that's simple. On integrated graphics the iGPU will use RAM, but it looks like you have quality on medium and texture compression on already. There might be some others you could look at (one about rotations?), but you'd probably reach diminishing returns there.

Beyond that, most memory (I think) is used for the simulation (it's not like Wube decided to use a bunch of RAM for absolutely no purpose), so really the only way to change that would be to have a smaller world. There are mods/scripts you can find to delete unused chunks around the periphery of your map (if you have a lot of area explored), but again there's only so far you can go there.

Eh.
Since I switched to Ubuntu a while ago Ive only had one crash. I can live with it.
But thanks anyways ^