[1.1.69] Crash when fueled spidertron changes surfaces with active logistics delivery

Bugs which we just recently fixed in our development version and will reach you in the next release.
Post Reply
Soggs
Inserter
Inserter
Posts: 20
Joined: Fri Sep 28, 2018 6:53 pm
Contact:

[1.1.69] Crash when fueled spidertron changes surfaces with active logistics delivery

Post by Soggs »

Yes the title is handful but it is really specific.

Steps to reproduce:
1. Load attached save with the mods
2. Enter the Spidertron(left)
3. Activate the logistics on the spidertron to trigger the delivery
4. Enter the Factorissimo building in front of you and crash

I left the Spiderling(right) in to demonstrate that it is for some reason related to needing fuel. I did test with another modded Spidertron that used fuel without a burn result and that also crashes.

Code: Select all

  54.468 Error CrashHandler.cpp:494: Exception Code: c0000005, Address: 0x00007ff6b38019ad
ModuleBase: 0x00007ff6b3430000, ImageSize: 01dfc000, RelativeAddress: 003d19ad
  54.468 Error CrashHandler.cpp:500: Access Violation: Read at address 0000000000000000
  54.468 Error CrashHandler.cpp:514: Exception Context:
rax=00007ff6b48f9508, rbx=0000000000000058, rcx=0000000000000000,
rdx=0000000000000001, rsi=000001d187966320, rdi=000001d151711320,
rip=00007ff6b38019ad, rsp=0000002e5624da88, rbp=0000002e5624db50,
 r8=00000000fffffffe,  r9=0000002e5624db50, r10=000001d17d5a9958,
r11=1160000000000099, r12=0000000000000032, r13=000001d187966320,
r14=000000000000000a, r15=000000000000000a
  54.468 Crashed in C:\Factorio Standalone\bin\x64\factorio.exe (0x00007ff6b3430000 - 0x00007ff6b522c000)
Factorio crashed. Generating symbolized stacktrace, please wait ...
c:\tmp\factorio-build-yc10jt\libraries\stackwalker\stackwalker.cpp (924): StackWalker::ShowCallstack
c:\tmp\factorio-build-yc10jt\src\util\logger.cpp (316): Logger::writeStacktrace
c:\tmp\factorio-build-yc10jt\src\util\logger.cpp (323): Logger::logStacktrace
c:\tmp\factorio-build-yc10jt\src\util\crashhandler.cpp (186): CrashHandler::writeStackTrace
c:\tmp\factorio-build-yc10jt\src\util\crashhandler.cpp (543): CrashHandler::SehHandler
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB49250057)
00007FFB49250057 (KERNELBASE): (filename not available): UnhandledExceptionFilter
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB4C115470)
00007FFB4C115470 (ntdll): (filename not available): memset
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB4C0FC7B6)
00007FFB4C0FC7B6 (ntdll): (filename not available): _C_specific_handler
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB4C11235F)
00007FFB4C11235F (ntdll): (filename not available): _chkstk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB4C0C14A4)
00007FFB4C0C14A4 (ntdll): (filename not available): RtlRaiseException
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB4C110E8E)
00007FFB4C110E8E (ntdll): (filename not available): KiUserExceptionDispatcher
c:\tmp\factorio-build-yc10jt\src\entity\spidervehicle.cpp (1268): SpiderVehicle::getInventory
c:\tmp\factorio-build-yc10jt\src\entity\spidervehicle.cpp (1649): SpiderVehicle::canHoldAtLeast
c:\tmp\factorio-build-yc10jt\src\item\inventoryreader.cpp (123): InventoryReader::canHoldAtLeast
c:\tmp\factorio-build-yc10jt\src\logistics\logisticpoint.cpp (430): LogisticPoint::cancelFromTargetedForDeliver
c:\tmp\factorio-build-yc10jt\src\logistics\logisticdeliverinterface.cpp (56): LogisticDeliverInterface::cancelOrder
c:\tmp\factorio-build-yc10jt\src\logistics\logisticnetwork.cpp (528): LogisticNetwork::removeLogisticMember
c:\tmp\factorio-build-yc10jt\src\logistics\logisticmember.cpp (58): LogisticMember::onDestroy
c:\tmp\factorio-build-yc10jt\src\logistics\logisticpoint.cpp (933): LogisticPoint::onDestroy
c:\tmp\factorio-build-yc10jt\src\entity\spidervehicle.cpp (1126): SpiderVehicle::onDestroy
c:\tmp\factorio-build-yc10jt\src\entity\entity.cpp (337): Entity::forceDestroy
c:\tmp\factorio-build-yc10jt\src\entity\spidervehicle.cpp (1044): SpiderVehicle::changeSurfaceAndPosition
c:\tmp\factorio-build-yc10jt\src\script\luacontrol.cpp (987): LuaControl::luaTeleport
c:\tmp\factorio-build-yc10jt\src\script\luabinder.hpp (348): LuaBinder<LuaCustomInputPrototype>::callWrapperOnObject
c:\tmp\factorio-build-yc10jt\libraries\lua\ldo.c (350): luaD_precall
c:\tmp\factorio-build-yc10jt\libraries\lua\lvm.c (713): luaV_execute
c:\tmp\factorio-build-yc10jt\libraries\lua\lapi.c (1067): f_call
c:\tmp\factorio-build-yc10jt\libraries\lua\ldo.c (137): luaD_rawrunprotected
c:\tmp\factorio-build-yc10jt\libraries\lua\ldo.c (623): luaD_pcall
c:\tmp\factorio-build-yc10jt\libraries\lua\lapi.c (1093): lua_pcallk
c:\tmp\factorio-build-yc10jt\src\util\luahelper.cpp (4341): LuaHelper::pCallWithStackTrace
c:\tmp\factorio-build-yc10jt\src\script\luagamescript.cpp (1140): LuaGameScript::runNthTickHandler
c:\tmp\factorio-build-yc10jt\src\script\luaeventdispatcher.cpp (132): LuaEventDispatcher::dispatch
c:\tmp\factorio-build-yc10jt\src\scenario\scenario.cpp (1286): Scenario::update
c:\tmp\factorio-build-yc10jt\src\scenario\scenario.cpp (1181): Scenario::updateStep
c:\tmp\factorio-build-yc10jt\src\mainloop.cpp (1252): MainLoop::gameUpdateStep
c:\tmp\factorio-build-yc10jt\src\mainloop.cpp (1108): MainLoop::gameUpdateLoop
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\include\functional (15732480): std::_Func_impl_no_alloc<<lambda_26782efc31a7be3e003a959977aedce1>,void>::_Do_call
c:\tmp\factorio-build-yc10jt\src\util\workerthread.cpp (49): WorkerThread::loop
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\include\thr\xthread (230): std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl RazerChromaController::*)(void),RazerChromaController *>,std::default_delete<std::tuple<void (__cdecl RazerChromaController::*)(void),RazerChromaController *> > > >::_Go
c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\include\thr\xthread (209): std::_Pad::_Call_func
minkernel\crts\ucrt\src\appcrt\startup\thread.cpp (97): thread_start<unsigned int (__cdecl*)(void *),1>
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB49CE7034)
00007FFB49CE7034 (KERNEL32): (filename not available): BaseThreadInitThunk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFB4C0C26A1)
00007FFB4C0C26A1 (ntdll): (filename not available): RtlUserThreadStart
Attachments
CrashTestSave.zip
(2.12 MiB) Downloaded 7 times
factorio-previous.log
(22.94 KiB) Downloaded 7 times
factorio-dump-previous.dmp
(786.54 KiB) Downloaded 6 times

Rseding91
Factorio Staff
Factorio Staff
Posts: 12341
Joined: Wed Jun 11, 2014 5:23 am
Contact:

Re: [1.1.69] Crash when fueled spidertron changes surfaces with active logistics delivery

Post by Rseding91 »

Thanks for the report. I saw these crash logs in the automatic crash reports and fixed it yesterday.

The fix will be out in the next 1.1 release.
If you want to get ahold of me I'm almost always on Discord.

Soggs
Inserter
Inserter
Posts: 20
Joined: Fri Sep 28, 2018 6:53 pm
Contact:

Re: [1.1.69] Crash when fueled spidertron changes surfaces with active logistics delivery

Post by Soggs »

Yeah, we probably produced them for a few days via the server and connected clients before I figured it out. At least there is a workaround for the moment to save the run.

User avatar
Jon8RFC
Filter Inserter
Filter Inserter
Posts: 536
Joined: Tue May 10, 2016 3:39 pm
Contact:

Re: [1.1.69] Crash when fueled spidertron changes surfaces with active logistics delivery

Post by Jon8RFC »

Rseding91 wrote:
Wed Sep 21, 2022 2:21 pm
Thanks for the report. I saw these crash logs in the automatic crash reports and fixed it yesterday.

The fix will be out in the next 1.1 release.
I know it's probably too short of notice, but I was just texting a friend about certain things I appreciate about Factorio and its development and it made me want to ask that you contribute some data to the FFF tomorrow...
Have some crash log data/graphs you can share with us, or even some performance things you've worked on for 1.2 or the expansion? It doesn't have to be "wow" factor stuff, just the same awesome stuff you've posted like "updated the loading so that instead of 0.75 seconds it takes only 0.3 seconds...and it'll scale if you load way more mods than any normal human should".
You know we appreciate that stuff like you do!
Image

Post Reply

Return to “Resolved for the next release”