Factorio Forums

Hey

Here's a small bug report; I was debugging a mod (attached) using serpent print in log files.
I suspect something with accessing the log file

First occurrence
- mod under dev is a local fork of nixie tubes 1.1.5 : adding support for color coding. Mod is provided for debug, open source but it's anything but stable
-- latest change was commenting out many log() calls
- log file (and mod source) is being monitored by up to date sublime text, that reloads pretty often. It seems
- Load save file (that uses many mods to mirror a gameplay). Relevant mods are gbd-nixie (under development) and SE that provides additional signals for colors
- build a few entities manually for stressing the debug, according to screenshot
- attempt to set an arithmetic combinator (see screenshot)
- for some reason, sublime text took unexpectedly long time to load the log file
- factorio crashes


Attchments : https://drive.filen.io/d/b27d1f45-8945- ... UFNIlEGqBR
- save game
- mod under dev
- screenshot at crash time
- factorio log
- mods list and config

Some more details:

- Could not reproduce
- During this debug session, I had much larger log files (Cant remember if that was 1.2M or 12M entries, but much larger). They were painful to load so I restarted the game when it was too big

If it's linked with the log file, it's probably not size only.

Unfortunately the log file also doesn't show anything interesting in the stack trace (it's essentially empty)