I have no idea what I was doing that would replicate this -- I think I was scrolling to try to zoom out while having hovered over something?
Anyway, save file and log are attached. Hopefully those are more useful than my memory of my actions is.
[0.17.74] Crash: "traversestrongtable at .../lgc.c:437"
-
- Fast Inserter
- Posts: 122
- Joined: Fri Jun 17, 2016 8:17 pm
- Contact:
[0.17.74] Crash: "traversestrongtable at .../lgc.c:437"
- Attachments
-
- _autosave1.zip
- (8.98 MiB) Downloaded 99 times
-
- factorio-current.log
- (44.4 KiB) Downloaded 105 times
Re: [0.17.74] Crash: "traversestrongtable at .../lgc.c:437"
Thanks for the report. Based off where it crashed it makes me think memory corruption/hardware issue on your end. Can you try running something like memtest86+ and see if it shows anything?
If you want to get ahold of me I'm almost always on Discord.
-
- Fast Inserter
- Posts: 122
- Joined: Fri Jun 17, 2016 8:17 pm
- Contact:
Re: [0.17.74] Crash: "traversestrongtable at .../lgc.c:437"
Well, I was thinking that was quite the improbable reason, but a kernel memtest came back with two failing bytes.
It's circumstantial at best (since vmem means we have no idea if Factorio was sitting on 0x00000003917af088 at the time), but seems like a reasonably compelling explanation if nobody else hits the same thing.
That particular savegame worked fine when I reloaded and continued (though of course my user inputs were different).
It's circumstantial at best (since vmem means we have no idea if Factorio was sitting on 0x00000003917af088 at the time), but seems like a reasonably compelling explanation if nobody else hits the same thing.
That particular savegame worked fine when I reloaded and continued (though of course my user inputs were different).