On a dedicated server (Windows 10 - GTX Gaming)
Running 1.1.82 with several mods (K2 SE and several others). I've had a couple of crashes this morning immediately after an auto-save. The most recent logs and dump file are attached. Not sure what other information is needed.
Exerpt from log file
2228.219 Info AppManager.cpp:306: Saving to _autosave3 (blocking).
2229.386 Info AppManagerStates.cpp:1917: Saving finished
2249.372 Error CrashHandler.cpp:635: Received SIGSEGV
Factorio crashed. Generating symbolized stacktrace, please wait ...
[1.1.82] Crash in lua
[1.1.82] Crash in lua
- Attachments
-
- K2SECrashed.zip
- The save file created just before the crash (renamed from _autosave3.zip)
- (10.07 MiB) Downloaded 37 times
-
- factorio-previous.log
- Log file from session that crashed
- (77 KiB) Downloaded 46 times
-
- factorio-dump-previous.dmp
- Generated dmp file
- (757.54 KiB) Downloaded 39 times
-
- factorio.zip
- Save file that was used to launch the server
- (9.79 MiB) Downloaded 40 times
Re: [1.1.82] Crash in lua
Thanks for the report. Based off where it's crashing it makes me suspect system instability and memory corruption due to that.
Do you have any reliable way to reproduce the crash? Something like "Load the save, let it run for 1 minute 43 seconds and it will crash"?
Do you have any reliable way to reproduce the crash? Something like "Load the save, let it run for 1 minute 43 seconds and it will crash"?
If you want to get ahold of me I'm almost always on Discord.
Re: [1.1.82] Crash in lua
You may be right. I was just seting up GTX to give them a try. Didn't capture the first crash. In the 24 hrs since then I have have had a few _different_ issues. I'll load this back up on a different service and see what happens.
Re: [1.1.82] Crash in lua
I have several hours (and auto-saves) hosting the game on another service without issue. As you suggested, I think the hosting service may have been having issues. Thanks for the analysys of the dump, and sorry for the goose chase.
-Kryo
-Kryo