[FIXED INTERNALLY]Server Crashes since today's open beta release.

So since Patching the Server today gone from stable to basically highly unstable with crashes happening almost ever hour or so.

The logs are being automatically reported but I've dropboxed them here: https://www.dropbox.com/sh/tqn04pbyhq1mkpb/AAD5Wy5dD37Qo0X5YTulAW-ta?dl=0 but a string of Access Violations all at the same memory address each time these were NOT happening prior to the open beta patch today.

2019-10-11 17:46:58.722 INFO    EDCORE: # -------------- 20191011-174659 --------------
2019-10-11 17:46:58.723 INFO    EDCORE: DCS/2.5.5.37626 (x86_64; Windows NT 10.0.14393)
2019-10-11 17:46:58.723 INFO    EDCORE: D:\DCS World OpenBeta\bin\dcs.exe
2019-10-11 17:46:58.724 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at CE11DDA2 00:00000000

2019-10-11 19:24:22.034 INFO    EDCORE: try to write dump information
2019-10-11 19:24:22.035 INFO    EDCORE: # -------------- 20191011-192423 --------------
2019-10-11 19:24:22.035 INFO    EDCORE: DCS/2.5.5.37626 (x86_64; Windows NT 10.0.14393)
2019-10-11 19:24:22.036 INFO    EDCORE: D:\DCS World OpenBeta\bin\dcs.exe
2019-10-11 19:24:22.036 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at CE11DDA2 00:00000000


2019-10-11 19:58:52.530 INFO    EDCORE: try to write dump information
2019-10-11 19:58:52.532 INFO    EDCORE: # -------------- 20191011-195853 --------------
2019-10-11 19:58:52.532 INFO    EDCORE: DCS/2.5.5.37626 (x86_64; Windows NT 10.0.14393)
2019-10-11 19:58:52.533 INFO    EDCORE: D:\DCS World OpenBeta\bin\dcs.exe
2019-10-11 19:58:52.533 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at CE11DDA2 00:00000000

and these are actual hard crashes readable in the windows error logs as well.

-Rob

Same here,

Mostely about 10 minutes in game, it freezes and a Crash report is generated.

Sorry was not a server crash, but single player game crash.

That at least..Seems to be solved..

One way or the other the scenario I used was causing the problem.

Sorry was not a server crash, but single player game crash.

 

That at least..Seems to be solved..

One way or the other the scenario I used was causing the problem.

yeah but it shouldn't that's the point.

Case in point here, I ave crash logs for almost every hour for 14 hours until I decided to roll back to last weeks Open Beta, and I've not had a single crash in the 18 hours since I did that. Exact same mission, exact same server, just the DCS version changed.

Something is triggering a Memory Access Violation, at first I thought maybe it was the Helicopters again (wouldn't be the first time) but that doesn't seem the case. The exact situation when the crash happens isn't the same each time in the logs either, so all I can presume is that it's AI related or something.

Frustrating as hell.

Thanks for the logs,

 

we can see some scripting callback errors prior to the crash. Has the mission been checked for scripting errors?

 

thanks

newy I'm running the exact same script after rolling back wiht out any issues.

I had to roll it back the server was unstable and crashing every hour, so original F-16 release missions running fine no issues for 6 hours at a time.

update to currently Open Beta - Mission becomes unstable and crashes every 45 - 2 hrs at the most.

-Rob.

Newy, Might but at the same time, working one OB release fine, then broken the next with no changes to the Moose version etc, no changes to the Scripting etc.

That would suggest that the issues being caused by a change in the core simulation code interacting with the script yes, but in that case what was changed with the scripting engine that wasn't documented in the patch notes?

I don't recall seeing anything about Scritping function changes etc, and we can't trouble shoot what is causing a crash easily if those types of notes are missing/not documented either.. All we can do is go 'well its working fine with out a crash on DCS: DCS/2.5.5.36986 (x86_64; Windows NT 10.0.14393)

but the moment we switch to DCS: DCS/2.5.5.37626 (x86_64; Windows NT 10.0.14393)

we suddenly get the crashes.