I load up the game and play for a few minutes, it will freeze and then close. This also happens if i leave the game idle on the main menu or if im doing anything on my world. The crash appears to happen more when crafting or doing something with items in chests. I will add my save file and my mods folder in a google drive link to help with discovering the issue.
Game log:
https://drive.google.com/file/d/1LrLIDN ... sp=sharing
Save file:
https://drive.google.com/file/d/13Fuh44 ... sp=sharing
Mods folder:
https://drive.google.com/file/d/1vot6VT ... sp=sharing
[1.1.41] Crashes randomly when playing
Re: [1.1.41] My game crashes randomly when playing it.
That log does not show a crash, you have not even loaded the save yet.
-
KeepResearchinSpoons
- Long Handed Inserter
- Posts: 77
- Joined: Tue Dec 01, 2020 6:57 pm
- Contact:
Re: [1.1.41] Crashes randomly when playing
to my knowledge the thing like that can happen if you exceed your available ram;
i.e. I suspect a silent OOM killer.
Mods number, pagefile size, suspect ram texture streaming; thus may be the case.
Not sure why does it not go off the grid right at the startup, but maybe the "other" system has flukes?
Windows just kills the process without a "warning", just forces it quit instantly.
I am not as sure it looks this way in logs... But factorio could at least *try* to manage its own ram to stay in sensible (or configurable?) limits.
In present you need some shenanigans to prevent some DoS-level ram things like importing or making blups or a simple rendering.create_rect called from chat console in a loop with one or two "extra" zeroes for loopsize (or event) by an (unrecoverable) mistake. Same for a "failed" on_chunk_created and other 'while-true's that 'leak' ram in the process. If failed you are welcome to reboot the whole server (love it. yup), or your local pc, if the fail was due to your own foolish actions.
Usually not the issue, but the sky is the limit AND so is the prints in the average mp game number.
The guess is just a guess using prev exp, no strings attached. It may just be anything, since the logs are "silent" and we have no more info on the matter.
I.E. we _probably_ need more info on what is happening to cut out things like dead-bit-in-ram-at-high-address, oom, driverfault and other tricksies that may occur.
Pls provide us with more data to go snooping the bug around.
i.e. I suspect a silent OOM killer.
Mods number, pagefile size, suspect ram texture streaming; thus may be the case.
Not sure why does it not go off the grid right at the startup, but maybe the "other" system has flukes?
Windows just kills the process without a "warning", just forces it quit instantly.
I am not as sure it looks this way in logs... But factorio could at least *try* to manage its own ram to stay in sensible (or configurable?) limits.
In present you need some shenanigans to prevent some DoS-level ram things like importing or making blups or a simple rendering.create_rect called from chat console in a loop with one or two "extra" zeroes for loopsize (or event) by an (unrecoverable) mistake. Same for a "failed" on_chunk_created and other 'while-true's that 'leak' ram in the process. If failed you are welcome to reboot the whole server (love it. yup), or your local pc, if the fail was due to your own foolish actions.
Usually not the issue, but the sky is the limit AND so is the prints in the average mp game number.
The guess is just a guess using prev exp, no strings attached. It may just be anything, since the logs are "silent" and we have no more info on the matter.
I.E. we _probably_ need more info on what is happening to cut out things like dead-bit-in-ram-at-high-address, oom, driverfault and other tricksies that may occur.
Pls provide us with more data to go snooping the bug around.