SMM crashes after updating mods
log generated after SMM crashed while updating mods
this crash happens fairly frequently after updating mods; seems to be more common if SMM has been running for some time
20 Replies
crashed again after installing upgrades
i've turned debug logging on and will post the log the next time it crashes
@Mircea (Area Actions)
Unfortunately crashes won't usually be caught in the log, which makes them pretty annoying to debug, and no easy way to catch them when they happen on a library thread instead of the main thread
Run this SMM build (standalone, not an installer) from command prompt, and send the output of that after it crashes https://drive.google.com/file/d/1jXL0HQMO4sfqVLsH8YHuSfbp5zlHvFDi/view?usp=sharing
Google Docs
SatisfactoryModManager-debug.exe
got it, will update this thread if and when it crashes
hasn't crashed yet, but since some recent modlist update, SnapOn has updated to look like this. the right-side screen still shows correct data and the link to ficsit.app still works. i'm attaching a debug dump in case it might be useful
i'll also note that the console this is running it is generating errors by trying to look at my old steam installation of satisafactory; i moved satisfactory to a different steam library (on a different drive) when 1.0 came out so it would be on an SSD, and it's using that installation for most things, but there are errors about not finding stuff in the old location
that location is in my E drive steam library, but satisfactory is installed in my C drive steam library (C being a SSD, E being a spinny)
You'll find an
unknown entry in the Manage Servers menu in SMM, which you can remove, but it doesn't cause any issues, it's just ignoredi wondered if that might be what that was
SMM remembers old install paths too, but just ignores them if they are invalid, in case they ever become valid again (for example a remote server that is not reachable at the moment)
i've been getting the case where mods go into that half-disappeared state when they're updated on ficsit.app; this time it's SnapOn but in the past it's been other mods. it doesn't always happen
otherwse the only interesting console message is the recurring which i assume is due to that mod having metadata issues; ficsit.app shows it as having two releases both labeled as 1.1.31
Yeah, not sure how that ended up happening. Maybe we can remove one of the two in the future, when it's unlikely anyone still uses either of the duplicate versions
and now it's doing it for two mods:
i just noticed that this build is not respecting the "start manually" setting in mod manager settings
ok, it does, but only if i switch it off and back on again. maybe a problem with reading the settings file
and now there are three of them
It's a known issue, it's because the queue runner doesn't send the done event so that SMM can pause it, but couldn't find why. Thinking of it now, though, I did add another callback to that event, so maybe the queue library can only deal with one callback
Is this even after restarting SMM?
I haven't tried that because I'm hunting a crash that happens when smm is left open for long periods of time. in past experience it goes away on restart
the irregular listings have now resolved on their own, without restarting SMM
ok so the story now with "start manually" is that i have to reenable it (turn it off and back on again) after each time i apply changes
and now another irregular entry on the modlist appears after applying updates
note that this was not there after downloading updates from the web, it only appeared after i applied updates