1.2.6 Update 3 Server Crashes

[logo12307]

Damm crashes

 

In the past three weeks i was unable to Play only ONE evening without a Crash.

 

Please fix this guys!

 

My crash-logs:

Logs_crashes.zip

[Voodoo-chacal]

In the past three weeks i was unable to Play only ONE evening without a Crash.

 

Please fix this guys!

 

My crash-logs:

 

I'm having the same problem

[ENO]

^ In that case you'll have a crash and dump file for every one. Please post.

Edited November 10, 2013 by ENO

[ENO]

Another one incoming:

 

Problem signature:

Problem Event Name: BEX64

Application Name: DCS.exe

Application Version: 1.2.6.19532

Application Timestamp: 5260f1fc

Fault Module Name: Effects.dll

Fault Module Version: 1.2.6.19532

Fault Module Timestamp: 52580634

Exception Offset: 000000000009ead8

Exception Code: c0000005

Exception Data: 0000000000000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 060c

Additional Information 2: 060c6a79338f620f0e987d3333092972

Additional Information 3: 90d3

Additional Information 4: 90d3b4330e4b209276a203612305776a

 

 

(Might be worth mentioning this is a different mission than the one that usually experiences this problem)

crash 11.10.13.zip

Edited November 11, 2013 by ENO

[ENO]

Getting old. Fortunately this time the wartweasel mission didn't crash with effects.dll as it usually does. Logs to follow.

 

 

Problem signature:

Problem Event Name: BEX64

Application Name: DCS.exe

Application Version: 1.2.6.19532

Application Timestamp: 5260f1fc

Fault Module Name: StackHash_232c

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Offset: 00000000ffffffff

Exception Code: c0000005

Exception Data: 0000000000000008

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 232c

Additional Information 2: 232cf46ab2010420aa6637d14c4604b7

Additional Information 3: f413

Additional Information 4: f4139525c10a55d95655dd552e43e805

 

 

On an objective side- instead of using the ZIU-9 bus I made them different types of civilian transportation. I'll see if I can get some feedback on how or when it happened. Latest version of the mission is included.

crash 11.11.13.zip

Edited November 12, 2013 by ENO

[Wrecking Crew]

There are two sets of logs and two additional crash dumps in this zip.

 

Please fix before Friday :)

 

WC

[NineLine]

There are two sets of logs and two additional crash dumps in this zip.

 

Please fix before Friday :)

 

WC

 

Have you guys noticed any other steps that we might be able to use to reproduce? The last few we tried havent yielded anything yet, not saying they havent pinned down some crashes, just not related to any steps mentioned here so far. (also we test on newer versions so its possible some of the stuff effecting the current release have been solved already)

[ENO]

Grimes was saying transport.dll was a deep rooted problem but there was already lots of info on it- that's the one I'm getting with my killbox mission but it HAS to be done in the MP side of things otherwise it does not happen. Ive run it for hours in SP testing and within 5 minutes of MP it crashes every time. Effects.dll only happened once the busses in wartweasel started getting blown up and that's easy enough to initiate early but agin has to happen on MP. Each time that crash happens te busses are being blown up. Changing the busses to other vehicle types resulted in a different crash as demonstrated above- but still a crash.

Edited November 13, 2013 by ENO

[Wrecking Crew]

The logs I posted above were from two missions - the earlier one somewhat complex (Tbilisi Thunder) and the latter (Huey Apocalypse) is fairly stable in that it will run for days, resetting itself on completion.

 

When Tbilisi Thunder crashed last night there were about 17 Clients in it. I was in a Red GC slot and F2'ing a Blue on Red dogfight (was great fun to watch). There was a little bit of lagging on my end, and I was going back and forth between F2 and F10 but the views were slow to respond, then crashola. This mission has Dynamic Weather. Oh, it had been running fine for about 2 1/2 hours before the crash.

 

I then started the Huey mission and called it a night. Saw the crash logs this morning that happened about 0008 hours this morning. Regular weather in this one.

 

I can't put my finger on anything...

 

WC

[NineLine]

Grimes was saying transport.dll was a deep rooted problem but there was already lots of info on it- that's the one I'm getting with my killbox mission but it HAS to be done in the MP side of things otherwise it does not happen. Ive run it for hours in SP testing and within 5 minutes of MP it crashes every time. Effects.dll only happened once the busses in wartweasel started getting blown up and that's easy enough to initiate early but agin has to happen on MP. Each time that crash happens te busses are being blown up. Changing the busses to other vehicle types resulted in a different crash as demonstrated above- but still a crash.

 

 

Wart Weasel is the mission name? If so I submit it for the next test session. And see if we can crash it with your steps.

 

 

Edit: And for what its worth, I am very appreciative for the effort you guys make to try and report this stuff...

Edited November 13, 2013 by NineLine

[sslechta]

Sithspawn, here's a total shot in the dark but I've been following this thread:

 

TrackIR change in 1.2.6

 

There are some edits that Kuky made to the autoexec.cfg file that could be possibly used in troubleshooting multiplayer.

 

Like I said, extreme guess but something to look at.

[NineLine]

You never know, I'll leave it up to the server admins if they think any of it might help, but I am not sure it will.

[ENO]

That little note is worth a lot more than you could imagine, Sith. I'm also relieved to see you're still hunting things down for us, so let me please express my appreciation in return.

 

 

WartWeasel is the mission- but I can very easily adjust it so that the busses go through their routine at the beginning of the mission as opposed to the end. I'm ALMOST positive that effects.dll that I was getting all the time has something to do with them.

 

The transport.dll one is another heavy from Killbox Zulu Romeo- I would love to put those to work for you guys and can send you latest iterations of those missions for your upcoming sessions.

[ENO]

Sithspawn, here's a total shot in the dark but I've been following this thread:

 

TrackIR change in 1.2.6

 

There are some edits that Kuky made to the autoexec.cfg file that could be possibly used in troubleshooting multiplayer.

 

Like I said, extreme guess but something to look at.

 

Eh Sslechta... I'm always open to learning but looked over there and it's 11 pages- can you give me a basic idea of where to look for what you're talking about?

[NineLine]

That little note is worth a lot more than you could imagine, Sith. I'm also relieved to see you're still hunting things down for us, so let me please express my appreciation in return.

 

 

WartWeasel is the mission- but I can very easily adjust it so that the busses go through their routine at the beginning of the mission as opposed to the end. I'm ALMOST positive that effects.dll that I was getting all the time has something to do with them.

 

The transport.dll one is another heavy from Killbox Zulu Romeo- I would love to put those to work for you guys and can send you latest iterations of those missions for your upcoming sessions.

 

If you can rig it to blow up at the beginning of the mission send it my way...

[Wrecking Crew]

Here is another log package.

 

After I posted the last one ^^^, I put up Huey Apocalypse for the day. The time stamp indicates that the DCS Stopped Working message on Hollo Pointe occurred at about 1 1/2 hours later. This package is a single event set of files.

 

DCS -- If you want a copy of these missions, PM me and I will provide it privately.

 

WC

[ENO]

Okay- a couple steps here for Killbox since I've never had any trouble at all blowing it up at the very start:

 

What I'm assuming is that it has something to do with the mission scripting engine being unable to sync the "group to random zone" orders for the variety of convoys... The crashes don't happen until a couple of people are on the server. The crashes are always server side and clients generally ping-timeout but evidence of the crash is obvious much sooner. It happens as soon as a couple of blue aircraft enter the zone. Quite often if you're not on the server side you'll see vehicles start to float or just start driving through everything- off roads. It's important to note that all the convoys have "on road" instructions (the tanks up near Temryk too)- so when they start off roading you'll know that the server has crashed. ALWAYS Transport.dll.

 

As for the Wartweasel- again... server side crashes in MP setting only- The buses are being activated right at the beginning of the mission now and will basically hold for a few moments and then go about their business. I don't want to structure blowing them up wholesale too much in the event that some relation / causation things happen and blind us to the fact that something else is going wrong. You may want to set up an invisible air start slot close to the waypoint- most of the time I think guys are getting these errors it's while using gun or mav on those buses.

 

 

A couple other things happen around that time-

 

a) a boat offshore is late activated and goes about its route.

b) some speedboats are timed in eventually so that they make the beach just after the buses do.

c) AI from many of the vehicles is turned off (to simulate a retreat)

 

When I've had it happen before, we'd blown up a couple of buses before the game unhitched. Again- we noticed it originally when our weapons stopped killing vehicles. F2 views of other aircraft showed them blown up or flying through the earth... just a basic de-sync... while the server will have already crashed.

Wartweasel 1.2.6.test.miz

Eno's Killbox.1.2.6.m.miz

Edited November 14, 2013 by ENO
adding detail

[Azrayen]

Hi,

 

Are you interested in client crashes too?

 

While testing LotAtc with some pilots of my squad, I got around half of 6 pilots crashed. Server kept fine 'til end mission.

We nailed the problem to one of the client killing an IA radar asset (EWR or AWACS). I didn't kept the logs, but I will try to reproduce (even if only to be able to say it's not a LotAtc-related issue), so if it's of interest, I'll see to keep server and clients logs next times...

 

Cheers,

Az'

[Grimes]

Okay- a couple steps here for Killbox since I've never had any trouble at all blowing it up at the very start:

 

What I'm assuming is that it has something to do with the mission scripting engine being unable to sync the "group to random zone" orders for the variety of convoys... ALWAYS Transport.dll.

 

I was able to replicate the crashes with transport.dll and dynamically assigned tasks. I'll keep an eye on it with the tester version to see if it is fixed.

[Pman]

For what its worth the VA server is crashing a few times a day at the moment and we dont have any combat on our server

 

So whatever underlaying issue there is with weapons there is also something nothing to do with weapon fire as well

 

Pman

[NineLine]

For client crashes it would be better to start your own thread, unless it also brings down the server with it.

 

Hi,

 

Are you interested in client crashes too?

 

While testing LotAtc with some pilots of my squad, I got around half of 6 pilots crashed. Server kept fine 'til end mission.

We nailed the problem to one of the client killing an IA radar asset (EWR or AWACS). I didn't kept the logs, but I will try to reproduce (even if only to be able to say it's not a LotAtc-related issue), so if it's of interest, I'll see to keep server and clients logs next times...

 

Cheers,

Az'

[NineLine]

Can you give more detailed information and logs? What were you doing at the time, how many people on the server, and mods and such you might have loaded.

 

For what its worth the VA server is crashing a few times a day at the moment and we dont have any combat on our server

 

So whatever underlaying issue there is with weapons there is also something nothing to do with weapon fire as well

 

Pman

 

Thanks for commenting Grimes!

 

I was able to replicate the crashes with transport.dll and dynamically assigned tasks. I'll keep an eye on it with the tester version to see if it is fixed.

[Pman]

4 crash logs from the past day since update 3.

 

Can you give any hints to what might have been happening when these crashes occurred?

 

Can you give more detailed information and logs? What were you doing at the time, how many people on the server, and mods and such you might have loaded.

 

 

 

Thanks for commenting Grimes!

 

As per the above posts nothing has changed. Still same type of crashes.

 

As for what is happening, as you well know VA is a 24/7 server I am not on it all the time, I think Slick copied some of the Servman logs earlier in this thread.

 

As for mods etc, we have already established in previous threads that removing the mods and scripts makes zero difference, Therefore the problem lays with the simulator and not the mods as removing them would fix the crashes.

 

Therefore please pass this info quoted onto the testing team and get it looked at

 

Pman

[NineLine]

Thanks for the response. Although I need step to reproduce for them to look at, if you come up with anything let me know. As it is, some of the other server ops are giving us some (which I think are going to make it into the test session today) so I hope its all related.

 

As per the above posts nothing has changed. Still same type of crashes.

 

As for what is happening, as you well know VA is a 24/7 server I am not on it all the time, I think Slick copied some of the Servman logs earlier in this thread.

 

As for mods etc, we have already established in previous threads that removing the mods and scripts makes zero difference, Therefore the problem lays with the simulator and not the mods as removing them would fix the crashes.

 

Therefore please pass this info quoted onto the testing team and get it looked at

 

Pman

[Pman]

Thanks for the response. Although I need step to reproduce for them to look at, if you come up with anything let me know. As it is, some of the other server ops are giving us some (which I think are going to make it into the test session today) so I hope its all related.

 

If I was able to identify the problem I would, however thats not my role nor in my spec without access to trunk.

 

I report the bug and supplied the logs as requested and a copy of the latest mission (which is open to anyone who joins the server)

 

Nothing more I can do for you at the this point other then report that it still is not fixed.

 

Pman