Server crash with Ficsit Remote Monitoring
Just got a server crash with FRM:
Signal 11 caught.
Malloc Size=262146 LargeMemoryPoolOffset=262162
CommonUnixCrashHandler: Signal=11
[2024.11.29-22.22.30:077][893]LogCore: === Critical error: ===
Unhandled Exception: SIGSEGV: invalid attempt to read memory at address 0x0000001800000006
[2024.11.29-22.22.30:078][893]LogCore: Fatal error!
0x00007fdb42f937c9 libFactoryServer-FicsitRemoteMonitoring-Linux-Shipping.so!UFRM_Vehicles::getTruckStation(UObject) [C:/SatisfactoryModLoader/Mods/FicsitRemoteMonitoring/Source/FicsitRemoteMonitoring/Private/FRM_Vehicles.cpp:7]
0x00007fdb42fa7d2a libFactoryServer-FicsitRemoteMonitoring-Linux-Shipping.so!AFicsitRemoteMonitoring::getTruckStation(UObject, FRequestData, TArray<TSharedPtr<FJsonValue, (ESPMode)1>, TSizedDefaultAllocator<32> >&) [C:/SatisfactoryModLoader/Mods/FicsitRemoteMonitoring/Source/Thi
rdParty/uWebSockets/../../FicsitRemoteMonitoring/Public/FicsitRemoteMonitoring.h:474]
Full log linked
4 Replies
Got it to crash with the following pages :
* drone
* map
* overallprod
Detailed prod seems to be broken too, but does not generate a crash.
Power and Resource sink do work fine (as far as I can tell...)
CC @DarthPorisius
Due to Thanksgiving, I hadn't been able to upload, but I did have the build server recompile after the headers were updated on SML.
See: https://github.com/porisius/FicsitRemoteMonitoring/actions/runs/12078275382
GitHub
CI · porisius/FicsitRemoteMonitoring@7c7e5d4
Contribute to porisius/FicsitRemoteMonitoring development by creating an account on GitHub.
that can totally wait, as I'm going to bed in a few minutes 🙂