Crashes at Multiplayer Session (NewGroundAI(), WayPointClass(), GetUnitWeaponId())
-
Hi folks,
yesterday we had a multiplayer session with 20 Pilots and 1 ATC Officer.
We used Falcon BMS 4.33.1 64bit - Vanilla Korea Theater. We also used OSC Validator respectively the OSC AWACS Tool (was used by our precious ATC Officer ).
It was a standard Tactical Engagement (will post the link later) including A-G / A-A tasks.Suddenly while some of our guys were doing AAR, the game crashed for most of us. Only the server and two clients kept running. Some of the clients showed the infamous “blue text” / lag infos.
We collected 13 crash logs (dumps and screenshots are included) which you can download here (~45MB).Looking at the crash logs, one can clearly see a common pattern. There are three variants of stack traces:
First:
Call Stack: 0033:0000000004A5EB1F Falcon BMS.exe, NewGroundAI()+111 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\ground\gndai.cpp, line 256+15 byte(s), Parameters(0x0000000040DFF1F0 0x0000000028C7F030 0x00000000166B6230 0x0000000000000000) 0033:0000000004A5C2CB Falcon BMS.exe, GroundClass::Init()+667 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\ground\grndmain.cpp, line 273+34 byte(s), Parameters(0x000000002511A3C0 0x00000000166B6230 0x0000000040DFF1F0 0x0000000028C7F0D0) 0033:0000000004835797 Falcon BMS.exe, AddVehicleToSim()+407 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simlib\simobj.cpp, line 392, Parameters(0x0000000040DFF1F0 0x0000000028C7F030 0x0000000028C7F0D0 0x0000000000000001) 0033:0000000004835409 Falcon BMS.exe, AddObjectToSim()+361 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simlib\simobj.cpp, line 302+5 byte(s), Parameters(0x00000000942E8396 0x0000000000000000 0x000000002511A3C0 0x0000000028C7F000) 0033:00000000049A4466 Falcon BMS.exe, UnitClass::DeaggregateFromData()+1430 byte(s), d:\wip\bms\svn\source\rel-4.33\campaign\camplib\unit.cpp, line 2012, Parameters(0x00000000459E0066 0x0000000000000000 0x00000000942E83AF 0x0000000000000000) 0033:00000000044D68D2 Falcon BMS.exe, FalconSimCampMessage::Process()+594 byte(s), d:\wip\bms\svn\source\rel-4.33\falclib\messages\simcampmsg.cpp, line 197, Parameters(0x00000000723EFDE0 0x0000000000000000 0x0000000000000000 0x0000000004B86C58) 0033:0000000004977CB1 Falcon BMS.exe, VuMessage::Dispatch()+113 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vuevent.cpp, line 1031, Parameters(0x00000000148E4D80 0x00000000723EFDE0 0x0000000004C56000 0x0000000000000000) 0033:00000000049770A7 Falcon BMS.exe, VuMessageQueue::DispatchVuMessage()+199 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vuevent.cpp, line 352, Parameters(0x00000000148E4D80 0x00000000148EFFD0 0x00000000148EFFD0 0x000000001BDA4A7E) 0033:000000000496DA6C Falcon BMS.exe, VuMainThread::Update()+8188 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vu.cpp, line 1697+31 byte(s), Parameters(0x00000000148EFFD0 0x0000000000000003 0x0000000042800000 0x000000001F32D120) 0033:0000000004A68015 Falcon BMS.exe, RealTimeFunction()+149 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simdrive\rtloop.cpp, line 49, Parameters(0x0000000000000013 0x0000000000000004 0x0000000004B86AF0 0x000000001F32D120) 0033:000000000484493F Falcon BMS.exe, SimulationLoopControl::Loop()+1391 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simloop\simloop.cpp, line 501, Parameters(0x0000000000000000 0x0000000000000000 0x00000000251B83A0 0x00000000048443D0) 0033:00000000044C809D Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), d:\wip\bms\svn\source\rel-4.33\falclib\ehandler.cpp, line 1567+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0AD7 Falcon BMS.exe, _callthreadstartex()+23 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 376+13 byte(s), Parameters(0x0000000000000000 0x00000000251B83A0 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0C7E Falcon BMS.exe, _threadstartex()+258 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 354+5 byte(s), Parameters(0x0000000004AC0B7C 0x00000000251B83A0 0x0000000000000000 0x0000000000000000) 0033:00000000B21013D2 KERNEL32.DLL, BaseThreadInitThunk()+34 byte(s), Parameters(0x00000000B21013B0 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:00000000B2C354E4 ntdll.dll, RtlUserThreadStart()+52 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
Second:
Call Stack: 0033:00000000049A8EAB Falcon BMS.exe, UnitClass::GetUnitWeaponId()+43 byte(s), d:\wip\bms\svn\source\rel-4.33\campaign\camplib\unit.cpp, line 4824+3 byte(s), Parameters(0x00000000397CBE20 0x0000000004AB94EB 0x0000000000000048 0x000000008F3AC5B0) 0033:00000000049F1722 Falcon BMS.exe, BattalionClass::GetVehicleDeagData()+786 byte(s), d:\wip\bms\svn\source\rel-4.33\campaign\camptask\battalio.cpp, line 1782+18 byte(s), Parameters(0x000000008F04CD50 0x0000000000000000 0x000000008F01075F 0x00000000258BF000) 0033:00000000049A43FA Falcon BMS.exe, UnitClass::DeaggregateFromData()+1322 byte(s), d:\wip\bms\svn\source\rel-4.33\campaign\camplib\unit.cpp, line 1984+43 byte(s), Parameters(0x000000008F040080 0x0000000000000000 0x000000008F01075F 0x0000000000000000) 0033:00000000044D68D2 Falcon BMS.exe, FalconSimCampMessage::Process()+594 byte(s), d:\wip\bms\svn\source\rel-4.33\falclib\messages\simcampmsg.cpp, line 197, Parameters(0x0000000087E47200 0x0000000000000000 0x0000000000000000 0x0000000004B86C58) 0033:0000000004977CB1 Falcon BMS.exe, VuMessage::Dispatch()+113 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vuevent.cpp, line 1031, Parameters(0x000000001EF740E0 0x0000000087E47200 0x0000000004C56000 0x0000000000000000) 0033:00000000049770A7 Falcon BMS.exe, VuMessageQueue::DispatchVuMessage()+199 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vuevent.cpp, line 352, Parameters(0x000000001EF740E0 0x000000001271F610 0x000000001271F610 0x00000000638F4EF9) 0033:000000000496DA6C Falcon BMS.exe, VuMainThread::Update()+8188 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vu.cpp, line 1697+31 byte(s), Parameters(0x000000001271F610 0x0000000000000003 0x0000000042800000 0x000000001EBAC200) 0033:0000000004A68015 Falcon BMS.exe, RealTimeFunction()+149 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simdrive\rtloop.cpp, line 49, Parameters(0x0000000087942A81 0x0000000000000004 0x0000000004B86AF0 0x000000001EBAC200) 0033:000000000484493F Falcon BMS.exe, SimulationLoopControl::Loop()+1391 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simloop\simloop.cpp, line 501, Parameters(0x0000000000000000 0x0000000000000000 0x0000000022D649C0 0x00000000048443D0) 0033:00000000044C809D Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), d:\wip\bms\svn\source\rel-4.33\falclib\ehandler.cpp, line 1567+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0AD7 Falcon BMS.exe, _callthreadstartex()+23 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 376+13 byte(s), Parameters(0x0000000022D649C0 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0C7E Falcon BMS.exe, _threadstartex()+258 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 354+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000076D059BD kernel32.dll, BaseThreadInitThunk()+13 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000076E3A2E1 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
Third:
Call Stack: 0033:00000000049B4490 Falcon BMS.exe, WayPointClass::WayPointClass()+64 byte(s), d:\wip\bms\svn\source\rel-4.33\campaign\camplib\campwp.cpp, line 77, Parameters(0x00000000D0E72CA0 0x0000000000000003 0x0000000026CDF190 0x0000000026CDF0C0) 0033:00000000049A406E Falcon BMS.exe, UnitClass::DeaggregateFromData()+414 byte(s), d:\wip\bms\svn\source\rel-4.33\campaign\camplib\unit.cpp, line 1894+30 byte(s), Parameters(0x00000000D0E72CA0 0x0000000000000000 0x0000000052FC9FFD 0x0000000004470000) 0033:00000000044D68D2 Falcon BMS.exe, FalconSimCampMessage::Process()+594 byte(s), d:\wip\bms\svn\source\rel-4.33\falclib\messages\simcampmsg.cpp, line 197, Parameters(0x000000007A5C9110 0x0000000000000000 0x0000000000000000 0x0000000004B86C58) 0033:0000000004977CB1 Falcon BMS.exe, VuMessage::Dispatch()+113 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vuevent.cpp, line 1031, Parameters(0x000000001327DFF0 0x000000007A5C9110 0x0000000000000000 0x0000000000000014) 0033:00000000049770A7 Falcon BMS.exe, VuMessageQueue::DispatchVuMessage()+199 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vuevent.cpp, line 352, Parameters(0x000000001327DFF0 0x00000000131A8270 0x00000000131A8270 0x0000000034D24705) 0033:000000000496DA6C Falcon BMS.exe, VuMainThread::Update()+8188 byte(s), d:\wip\bms\svn\source\rel-4.33\vu2\src\vu.cpp, line 1697+31 byte(s), Parameters(0x00000000131A8270 0x0000000000000014 0x0000000000000000 0x0000000000000000) 0033:0000000004A68015 Falcon BMS.exe, RealTimeFunction()+149 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simdrive\rtloop.cpp, line 49, Parameters(0x0000000000000013 0x0000000000000004 0x0000000004B86AF0 0x000000001E17D590) 0033:000000000484493F Falcon BMS.exe, SimulationLoopControl::Loop()+1391 byte(s), d:\wip\bms\svn\source\rel-4.33\sim\simloop\simloop.cpp, line 501, Parameters(0x0000000000000000 0x0000000000000000 0x00000000236512B0 0x00000000048443D0) 0033:00000000044C809D Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), d:\wip\bms\svn\source\rel-4.33\falclib\ehandler.cpp, line 1567+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0AD7 Falcon BMS.exe, _callthreadstartex()+23 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 376+13 byte(s), Parameters(0x0000000000000000 0x00000000236512B0 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0C7E Falcon BMS.exe, _threadstartex()+258 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 354+5 byte(s), Parameters(0x0000000004AC0B7C 0x00000000236512B0 0x0000000000000000 0x0000000000000000) 0033:0000000018648102 KERNEL32.DLL, BaseThreadInitThunk()+34 byte(s), Parameters(0x00000000186480E0 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:000000001945C5B4 ntdll.dll, RtlUserThreadStart()+52 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
These three variants are scattered among the uploaded logs.
Please do also note, that all logs contain the clear text fragments “1532nd” and “1532nd SpecOps Battalion”:0x00000000258BF028: 00000000397CBE20 0000000700000007 000000003942E460 00000000397CBE20 .|9............`.B9.... .|9.... 0x00000000258BF048: 0000000000000000 000000FF00000000 00000000397CBE20 0000000000000080 ................ .|9............ 0x00000000258BF068: 0000000200000001 0000000200000080 49F5A35E49649F25 00000000C4320000 ................%.dI^..I..2..... 0x00000000258BF088: 0000000000000080 00000000258BF0C0 00000000258BF0B0 00000000258BF0D0 ...........%.......%.......%.... 0x00000000258BF0A8: 00000000258BF110 0000646E32333531 000000FF00000003 7325207325207325 ...%....1532nd..........%s %s %s 0x00000000258BF0C8: 0000638200000000 000000000000FFFF 0000000000000000 0000000000000000 .....c.......................... 0x00000000258BF0E8: 0000000000000000 000000FF00000003 FFFFFFFFFFFFFFFE 0000000004C56000 .........................`...... 0x00000000258BF108: 000000003942E460 0000000000000000 00000000005F3898 00000000397CBE20 `.B9.............8_..... .|9.... 0x00000000258BF128: 0000000087E47200 00000000258BF240 00000000044D68D2 000000008F040080 .r......@..%.....hM............. 0x00000000258BF148: 0000000000000000 000000008F01075F 0000000000000000 0000000058E9F340 [email protected].... 0x00000000258BF168: 0000000058E9F340 0000000000000000 0000000000000000 000000003ECAF2D0 @..X.......................>.... 0x00000000258BF188: FFFFFFFFFFFFFFFE 5320646E32333531 422073704F636570 6E6F696C61747461 ........1532nd SpecOps Battalion 0x00000000258BF1A8: BF8FCF41C0000000 BF412843E0000000 BF6E0676C0000000 0000000000000000 ....A.......C(A.....v.n......... 0x00000000258BF1C8: 0000000000000000 0000000000000000 00001B5800000000 0000000000000000 ....................X........... 0x00000000258BF1E8: C2A885D944296D68 040022F9413EE7F8 0000000058E9F340 0000000004C56000 hm)D......>A."[email protected].....`...... 0x00000000258BF208: 0000000004B86C58 00000000005F3898 0000000000000001 0000000000000000 Xl.......8_.....................
As usual, we are pretty clueless what exactly could have caused the crashes and why the server and some of the clients kept running .
The clients that kept running didn’t produce any debug information. Luckily one of them saved an ACMI which I can share later on - if necessary.As I mentioned above, I can provide the TE later on, as soon as I get my hands on it.
If you need any information, please let me know.There are similar reports on the forums already - one of them is also connected with a tanker in proximity of the flights:
- https://www.benchmarksims.org/forum/showthread.php?23931-Crash-in-MP-perhaps-some-interresting-data-inside&highlight=GetUnitWeaponId
- https://www.benchmarksims.org/forum/showthread.php?21323-CTD-stock-theater&highlight=WayPointClass
- https://www.benchmarksims.org/forum/showthread.php?23598-CTD-on-receiving-units&highlight=NewGroundAI
BTW: Thanks for this great game! While we experience problems like this from time to time - this doesn’t break the fun we have with this simulator! We appreciate your work a lot - so we’re happy to help to even improve it .
-
Blue text means bw issue. Probably Internet provider problem at the point?
Are there any packet losses or bw connection info?
Sorry can’t recall if network log is the same as before. Or can’t tell if your logs are crash logs or network logs.
Sent from TapaTalk -
Blue text means bw issue. Probably Internet provider problem at the point?
Are there any packet losses or bw connection info?
Sorry can’t recall if network log is the same as before. Or can’t tell if your logs are crash logs or network logs.
Sent from TapaTalkYes, that’s right - only a few flight members experienced the blue text, though. These are crash logs…
Can’t tell whether there are any network logs either. -
Hi,
as the server has run in DEBUG-Mode i’ve done some research in the *xlog.txt of the Server. I doubt that it has to do with the “1532nd SpecOps” because this unit appaers in the log already way before the crash of most of the clients happened.
I’m very confident it was MY connection that caused this problems: i have one of the two “dubious connections” in this session (had to use a crappy ISP router with non-working portforwarding because a lightning destroyed my good one) and that not enough i also have only 700 KB/s upload.
I was the lead of a 4-ship flight and we just arrived at an KC-10 for AAR. As i was the first one to refuel my BMS got the Tanker-Entity handed over by the server. Trying to connect i had heavy lags (2-3 secs.), at that point the clients began to drop out of the game.
Pretty sure the combination of my shitty connection and trying AAR caused the mission crash, whats the opinion of the BMS Tech-Pros?