Search the Community
Showing results for tags 'dedicated server crash'.
-
When you try and stop a dcs dedicated server it will crash out Stopping via either taskkill /IM dcs.exe or right clicking the window and then using close window results in this 2021-08-10 06:59:59.255 INFO Dispatcher: Stop 2021-08-10 06:59:59.271 INFO Scripting: event:type=mission end,t=28.946, 2021-08-10 06:59:59.368 INFO Config: netview stopped 2021-08-10 06:59:59.388 INFO DCS: wcTanker::onEvent:5 2021-08-10 06:59:59.388 INFO EDCORE: (wcTanker::Channel)enterToState_:6 2021-08-10 06:59:59.388 INFO EDCORE: (wcTanker)enterToState_:3 2021-08-10 06:59:59.388 INFO DCS: wcTanker::onEvent:5 2021-08-10 06:59:59.388 INFO EDCORE: (wcTanker::Channel)enterToState_:6 2021-08-10 06:59:59.388 WARNING LOG: 1 duplicate message(s) skipped. 2021-08-10 06:59:59.388 INFO EDCORE: (wcTanker)enterToState_:3 2021-08-10 06:59:59.388 INFO DCS: wcTanker::onEvent:5 2021-08-10 06:59:59.388 INFO EDCORE: (wcTanker::Channel)enterToState_:6 2021-08-10 06:59:59.388 WARNING LOG: 1 duplicate message(s) skipped. 2021-08-10 06:59:59.388 INFO EDCORE: (wcTanker)enterToState_:3 2021-08-10 06:59:59.571 INFO TERRAIN: lSystem::CleanScenes() 2021-08-10 06:59:59.572 INFO NET: simulation stopped, state=ssIdle 2021-08-10 06:59:59.704 INFO EDCORE: (dDispatcher)enterToState_:3 2021-08-10 06:59:59.709 INFO DCS: application shutdown 2021-08-10 07:00:00.944 INFO NET: server has stopped 2021-08-10 07:00:00.952 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 0 2021-08-10 07:00:00.959 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 1 2021-08-10 07:00:00.960 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 2 2021-08-10 07:00:01.134 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 3 2021-08-10 07:00:01.289 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 4 2021-08-10 07:00:01.300 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 5 2021-08-10 07:00:01.304 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 6 2021-08-10 07:00:01.309 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 7 2021-08-10 07:00:01.309 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 8 2021-08-10 07:00:01.322 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 9 2021-08-10 07:00:01.322 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 10 2021-08-10 07:00:01.324 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 11 2021-08-10 07:00:01.324 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 12 2021-08-10 07:00:01.325 INFO EDOBJECTS: lTypeObjectManagerImpl::clear 13 2021-08-10 07:00:02.003 INFO EDCORE: try to write dump information 2021-08-10 07:00:02.030 INFO EDCORE: # -------------- 20210810-070003 -------------- 2021-08-10 07:00:02.045 INFO EDCORE: DCS/2.7.4.9847 (x86_64; Windows NT 10.0.14393) 2021-08-10 07:00:02.068 INFO EDCORE: D:\games\DCS_dedi_beta\bin\ed_sound.dll 2021-08-10 07:00:02.083 INFO EDCORE: # C0000005 ACCESS_VIOLATION at FBCE5266 00:00000000 2021-08-10 07:00:02.114 INFO EDCORE: SymInit: Symbol-SearchPath: '.;D:\games\DCS_dedi_beta;D:\games\DCS_dedi_beta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'dcs' 2021-08-10 07:00:02.130 INFO EDCORE: OS-Version: 10.0.14393 () 0x110-0x3 2021-08-10 07:00:02.748 INFO EDCORE: 0x0000000000015266 (ed_sound): SND_speaker_layout_get_info + 0xBF6 2021-08-10 07:00:02.769 INFO EDCORE: 0x000000000001478E (ed_sound): SND_speaker_layout_get_info + 0x11E 2021-08-10 07:00:02.784 INFO EDCORE: 0x000000000000392A (ed_sound): SND_exit + 0xEA 2021-08-10 07:00:02.817 INFO EDCORE: 0x00000000007E78A2 (DCS): SW + 0x4F6DA2 2021-08-10 07:00:02.833 INFO EDCORE: 0x0000000001C6A7AF (DCS): AmdPowerXpressRequestHighPerformance + 0xE777AB 2021-08-10 07:00:02.848 INFO EDCORE: 0x0000000000A0A24E (DCS): SW + 0x71974E 2021-08-10 07:00:02.868 INFO EDCORE: 0x0000000000008364 (KERNEL32): BaseThreadInitThunk + 0x14 2021-08-10 07:00:02.884 INFO EDCORE: 0x0000000000067091 (ntdll): RtlUserThreadStart + 0x21 2021-08-10 07:00:02.976 INFO EDCORE: Minidump created. 2021-08-10 07:00:02.985 INFO Lua::Config: stack traceback:
-
Hi ED, For a long time we've been having issues with "bad waypoints" causing server crashes, whilst this has always been intermittent and with many tens of units being moved at a given time over the course of a PvP campaign it can be hard to find out which unit was moved from where to where that may have caused the crash. 2023-07-02 22:41:59.407 INFO EDCORE (8764): OS-Version: 10.0.20348 () 0x110-0x3 2023-07-02 22:41:59.416 INFO EDCORE (8764): 0x000000000006cb67 (edterrain4): buildMaxEdgeLengthUVSet + 0x1607 2023-07-02 22:41:59.430 INFO EDCORE (8764): 0x0000000000229e1f (edterrain4): landscape5::lsa5pureFile::Mesh::tinyCopy + 0x118F 2023-07-02 22:41:59.438 INFO EDCORE (8764): 0x0000000000230181 (edterrain4): landscape5::navGraph5File::findPath + 0x961 2023-07-02 22:41:59.462 INFO EDCORE (8764): 0x00000000002605a1 (edterrain4): navGraphPath2::save + 0x4471 -- 2023-07-02 22:45:09.218 INFO EDCORE (14644): OS-Version: 10.0.20348 () 0x110-0x3 2023-07-02 22:45:09.227 INFO EDCORE (14644): 0x000000000006cb67 (edterrain4): buildMaxEdgeLengthUVSet + 0x1607 2023-07-02 22:45:09.235 INFO EDCORE (14644): 0x0000000000229e1f (edterrain4): landscape5::lsa5pureFile::Mesh::tinyCopy + 0x118F 2023-07-02 22:45:09.244 INFO EDCORE (14644): 0x0000000000230181 (edterrain4): landscape5::navGraph5File::findPath + 0x961 2023-07-02 22:45:09.267 INFO EDCORE (14644): 0x00000000002605a1 (edterrain4): navGraphPath2::save + 0x4471 -- 2023-07-09 22:44:40.522 INFO EDCORE (15060): OS-Version: 10.0.20348 () 0x110-0x3 2023-07-09 22:44:40.530 INFO EDCORE (15060): 0x000000000006cb67 (edterrain4): buildMaxEdgeLengthUVSet + 0x1607 2023-07-09 22:44:40.539 INFO EDCORE (15060): 0x00000000002301bc (edterrain4): landscape5::navGraph5File::findPath + 0x99C 2023-07-09 22:44:40.549 INFO EDCORE (15060): 0x000000000026055e (edterrain4): navGraphPath2::save + 0x442E 2023-07-09 22:44:40.560 INFO EDCORE (15060): 0x000000000025ec62 (edterrain4): navGraphPath2::save + 0x2B32 -- 2023-07-17 02:35:36.722 INFO EDCORE (11376): OS-Version: 10.0.20348 () 0x110-0x3 2023-07-17 02:35:36.730 INFO EDCORE (11376): 0x000000000006cb67 (edterrain4): buildMaxEdgeLengthUVSet + 0x1607 2023-07-17 02:35:36.739 INFO EDCORE (11376): 0x00000000002301bc (edterrain4): landscape5::navGraph5File::findPath + 0x99C 2023-07-17 02:35:36.747 INFO EDCORE (11376): 0x000000000026055e (edterrain4): navGraphPath2::save + 0x442E 2023-07-17 02:35:36.756 INFO EDCORE (11376): 0x000000000025ec62 (edterrain4): navGraphPath2::save + 0x2B32 -- 2023-07-20 19:08:45.377 INFO EDCORE (6160): OS-Version: 10.0.20348 () 0x110-0x3 2023-07-20 19:08:45.388 INFO EDCORE (6160): 0x000000000006cb67 (edterrain4): buildMaxEdgeLengthUVSet + 0x1607 2023-07-20 19:08:45.398 INFO EDCORE (6160): 0x00000000002301bc (edterrain4): landscape5::navGraph5File::findPath + 0x99C 2023-07-20 19:08:45.407 INFO EDCORE (6160): 0x000000000025e8a1 (edterrain4): navGraphPath2::save + 0x2771 2023-07-20 19:08:45.418 INFO EDCORE (6160): 0x000000000025f032 (edterrain4): navGraphPath2::save + 0x2F02 However after the most recent one, we were fortunate the user knew exactly which unit and where it was moved to - enabling me to get an almost 100% reproducible setup in the ME - Open Beta 2.8.6.41363 - No Mods For a first hand, just jump into taccom, select the Leclerc and set a way point to +41666 +4712 and you should experience a game crash, if it succeeds in calculating a route, set the way point again in a similar area and it should fail to calculate and crash. This isn't unique to Syria, or Bassel (though we have had 3 crashes with units around basal in particular, so seems to be more prone to occur around here) Please find attached track replay. dcs.log-20230720-200509.zip