Page 1 of 1

[Dominik][0.17.56] Crash: LatencyState::buildItem + LatencyState::fillBeltGap

Posted: Wed Jul 17, 2019 4:36 pm
by AreYouScared
This was reported to us, Clusterio staff, when it should've been reported here.
Bilka requested a bug report to be posted

Code: Select all

Generating symbolized stacktrace, please wait ...
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD585FDE4)
00007FFAD585FDE4 (ntdll): (filename not available): NtDelayExecution
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD1BF96C1)
00007FFAD1BF96C1 (KERNELBASE): (filename not available): SleepEx
f:\dd\vctools\crt\crtw32\stdcpp\thr\cthread.c (68): _Thrd_sleep
c:\cygwin64\tmp\factorio-build-lgbomw\src\util\crashhandler.cpp (432): CrashHandler::SehHandler
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD1C46B2C)
00007FFAD1C46B2C (KERNELBASE): (filename not available): UnhandledExceptionFilter
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD58681CB)
00007FFAD58681CB (ntdll): (filename not available): memset
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD584FD56)
00007FFAD584FD56 (ntdll): (filename not available): _C_specific_handler
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD586477F)
00007FFAD586477F (ntdll): (filename not available): _chkstk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD57C4BEF)
00007FFAD57C4BEF (ntdll): (filename not available): RtlWalkFrameChain
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD58634EE)
00007FFAD58634EE (ntdll): (filename not available): KiUserExceptionDispatcher
c:\cygwin64\tmp\factorio-build-lgbomw\src\latencystate.cpp (525): LatencyState::buildItem
c:\cygwin64\tmp\factorio-build-lgbomw\src\latencystate.cpp (508): LatencyState::fillBeltGap
c:\cygwin64\tmp\factorio-build-lgbomw\src\latencyinputhandler.cpp (484): LatencyInputHandler::buildItem
c:\cygwin64\tmp\factorio-build-lgbomw\src\latencyinputhandler.cpp (799): LatencyInputHandler::update
c:\cygwin64\tmp\factorio-build-lgbomw\src\mainloop.cpp (1169): MainLoop::gameUpdateStep
c:\cygwin64\tmp\factorio-build-lgbomw\src\mainloop.cpp (1021): MainLoop::gameUpdateLoop
c:\cygwin64\tmp\factorio-build-lgbomw\src\util\workerthread.cpp (42): WorkerThread::loop
c:\program files (x86)\microsoft visual studio\2017\buildtools\vc\tools\msvc\14.15.26726\include\thr\xthread (230): std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl*)(ParallelScenarioSaver *),ParallelScenarioSaver *>,std::default_delete<std::tuple<void (__cdecl*)(ParallelScenarioSaver *),ParallelScenarioSaver *> > > >::_Go
c:\program files (x86)\microsoft visual studio\2017\buildtools\vc\tools\msvc\14.15.26726\include\thr\xthread (209): std::_Pad::_Call_func
minkernel\crts\ucrt\src\appcrt\startup\thread.cpp (115): thread_start<unsigned int (__cdecl*)(void * __ptr64)>
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD2A37974)
00007FFAD2A37974 (KERNEL32): (filename not available): BaseThreadInitThunk
ERROR: SymGetLineFromAddr64, GetLastError: 487 (Address: 00007FFAD582A271)
00007FFAD582A271 (ntdll): (filename not available): RtlUserThreadStart
20603.280 Error Util.cpp:97: Unexpected error occurred. If you're running the latest version of the game you can help us solve the problem by posting the contents of the log file on the Factorio forums.
Please also include the save file(s), any mods you may be using, and any steps you know of to reproduce the crash.
20610.741 Uploading log file
The full crash can be viewed here

Or the users log they provided and be downloaded

User stated: Crash happened while I was in a train and placed a station in front of me.

Devs : If you're in the GridLock discord, user is in #bug-0105

Re: [Dominik][0.17.56] Crash: LatencyState::buildItem + LatencyState::fillBeltGap

Posted: Mon Jul 22, 2019 9:41 am
by Dominik
Hi, thanks for bringing it up.
This is related to the belt building when moving very fast. Since there were no issues with it for a very long time, I think it is likely a result of another bug/random error. Nevertheless, I have added yet another prevention of the issue, one that is already present in similar logic of power pole building.