1.2.6 Update 3 Server Crashes

NineLine · October 22, 2013

Please try and include logs, dmp files and tracks, as well, when possible, try and if possible, clues to what might have been going on when crash occurred.

Couple crashes that were fixed with this update, but you might want to keep an eye on if you see problems:

- Multiplayer: Fixed crash when one player performs belly landing.

- Su-25T: Fixed crash when Kh-25MPU is launched when seeker deflection is too great.

Possible crash causes that have not been confirmed or verified:

- Large amount of units moved as ground commander

- Mortar units given targets to fire on

- Mi8 firing weapons

Edited October 22, 2013 by NineLine

ENO · October 23, 2013

Good luck you guys! Don't forget to save new versions of your missions and restart after you update!

sslechta · October 23, 2013

VA Server still crashing after the most recent updates to DCS. 5 crashes in the past 24 hours....

NineLine · October 23, 2013

VA Server still crashing after the most recent updates to DCS. 5 crashes in the past 24 hours....

Can you dig for any hard data, perhaps a general time that it happens, perhaps a point in the mission you are using, perhaps try changing the mission (if you havent already) to see if that makes a difference... anything substantial that we can test.

FlightControl · October 23, 2013

Dear Ed development team,

Run my mission for 2 hours. Pls put debug mode on. When you get the crash, observe where it happened, check the memory and the call stack. And try to trace back the error. Sure there are multple conditions that cause crashes.

I know the simulation software is very complicated and demanding to debug. But right now multiplayer is simply not working. I ran my server yesterday for two hours, and got two crashes...

So, i am happy to assist with testing. Find my previous posts on crash logs etc. Is this request reasonable?

Sven

NineLine · October 23, 2013

Dear Ed development team,

Run my mission for 2 hours. Pls put debug mode on. When you get the crash, observe where it happened, check the memory and the call stack. And try to trace back the error. Sure there are multple conditions that cause crashes.

I know the simulation software is very complicated and demanding to debug. But right now multiplayer is simply not working. I ran my server yesterday for two hours, and got two crashes...

So, i am happy to assist with testing. Find my previous posts on crash logs etc. Is this request reasonable?

Sven

Sorry can you post your mission here, also, do you see anything happen at the same time as the crash on a regular basis?

FlightControl · October 23, 2013

Can you dig for any hard data, perhaps a general time that it happens, perhaps a point in the mission you are using, perhaps try changing the mission (if you havent already) to see if that makes a difference... anything substantial that we can test.

Sorry can you post your mission here, also, do you see anything happen at the same time as the crash on a regular basis?

http://forums.eagle.ru/showthread.php?t=110990

So, run this mission for 2 hours in debug mode, and check if it crashes. And where...

Additional note:

I have done multiple changes in my mission. Note that i have ground troops, ships, and dynamic spawning of units. And anti ship missiles.

One thing to add: i've noticed that the effectiveness of antiship missiles have been greatly improved over the last releases. Since release 1.2.5 anti ship missiles were hardly effective. That has been fixed, thanks ed for that.

In the meanwhile, i am going to make subversions of this mission, and try to measure the effects of downsizing. F.e., only spawning one category without ground troops etc.

Sven

NineLine · October 23, 2013

Ok, I will have a look at it later, and see if we can use it in one of our testing sessions.

http://forums.eagle.ru/showthread.php?t=110990

So, run this mission for 2 hours in debug mode, and check if it crashes. And where...

Additional note:
I have done multiple changes in my mission. Note that i have ground troops, ships, and dynamic spawning of units. And anti ship missiles.
One thing to add: i've noticed that the effectiveness of antiship missiles have been greatly improved over the last releases. Since release 1.2.5 anti ship missiles were hardly effective. That has been fixed, thanks ed for that.

In the meanwhile, i am going to make subversions of this mission, and try to measure the effects of downsizing. F.e., only spawning one category without ground troops etc.

Sven

FlightControl · October 23, 2013

Ok, I will have a look at it later, and see if we can use it in one of our testing sessions.

Thank you. In the meanwhile, i will upload my latest latest version resaved with the mission editor of update 3, which is still on my local machine.

I will edit the first post of the thread where the mission is saved with the latest version, and will make a post in my thread noting the update.µ

kind regards,

Sven

sslechta · October 23, 2013

4 crash logs from the past day since update 3.

DCS-20131023-CrashLogs.zip

NineLine · October 23, 2013

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?

sslechta · October 23, 2013

Here are servlog/chatlogs.... I blocked usernames/IPs for their protection.... No common reason during those crashes.

Logs below are taken during the couple of minutes up to each crash provided above.....

SERVLOG
10/22/13 22:06:58 : SERVER:on_connect(5, 2XX.XX.157.195, 49258, "LuXXXXXXXXX", "7f60058b6cc47f90e76a5599ba3f91f6")
10/22/13 22:07:19 : SERVER:on_connect(11, 9X.XX.240.42, 56502, "SXXXX", "be97be809dba7056f45ad08918133a6d")
10/22/13 22:07:24 : Client [20] "JXXXX" joined Blue in "UH-1H"(10)
10/22/13 22:07:37 : SERVER:on_connect(12, 8X.XX.164.240, 52706, "SXXXXX", "7a224776d5eef3d65f45499998c40e31")
10/22/13 22:07:46 : Client [11] "SXXXX" joined Blue in "A-10C"(35)
CHATLOG
10/22/13 22:06:24 : [14] "BXXXX" : [14] "BXXXX" made a screenshot
10/22/13 22:06:28 : [14] "BXXXX" : [14] "BXXXX" made a screenshot
10/22/13 22:06:58 : [1] "SERVER-ADMIN" : "LXXXXXX" entered the game.
10/22/13 22:07:19 : [1] "SERVER-ADMIN" : "SXXXXXX" entered the game.
10/22/13 22:07:24 : [1] "SERVER-ADMIN" : "JXXXXXX" joined BLUE in UH-1H.
10/22/13 22:07:37 : [1] "SERVER-ADMIN" : "SXXXXXX" entered the game.
10/22/13 22:07:46 : [1] "SERVER-ADMIN" : "SXXXXXX" joined BLUE in A-10C.

SERVLOG
10/23/13 00:05:10 : TAKE-OFF: Player id = [4], BLUE player "VXXXXXX" took off.
10/23/13 00:05:40 : LANDING: Player id = [8], BLUE player "VBXXXXXX" landed.
10/23/13 00:05:57 : TAKE-OFF: Player id = [8], BLUE player "VBXXXXXX" took off.
10/23/13 00:06:27 : TAKE-OFF: Player id = [9], BLUE player "VXXXXXX" took off.
10/23/13 00:06:28 : TAKE-OFF: Player id = [3], BLUE player "VXXXXXX" took off.
CHATLOG
10/23/13 00:00:24 : [1] "SERVER-ADMIN" : "VXXXXXXXXX" joined BLUE in Su-33.
10/23/13 00:00:27 : [1] "SERVER-ADMIN" : "VXXXXXXXXX" joined BLUE in Su-33.
10/23/13 00:01:04 : [1] "SERVER-ADMIN" : "VXXXXXXXXX" joined BLUE in Su-33.
10/23/13 00:01:12 : [8] "VBXXXXXXX" : lol
10/23/13 00:02:34 : [1] "SERVER-ADMIN" : BLUE player "VXXXXXX" crashed.
10/23/13 00:03:44 : [1] "SERVER-ADMIN" : BLUE player "VBXXXXX" crashed.
10/23/13 00:04:10 : [6] "sXXXXX" : inbound the vinson

SERVLOG
10/23/13 16:52:58 : Disconnected client: [2] "toXXXXXX"
10/23/13 16:53:08 : Disconnected client: [6] "M3XXXXXXX"
10/23/13 16:53:11 : LANDING: Player id = [11], BLUE player "CXXXXXXX" landed.
10/23/13 16:53:12 : MISSION RESTART in: 1 hour(s)
10/23/13 16:53:59 : Disconnected client: [11] "CXXXXXXXXXX"
10/23/13 16:54:15 : CRASH: Player id = [19], name = "DXXXXXXXX" crashed.
CHATLOG
10/23/13 16:53:20 : [13] "AXXXXXXXX" : wow good landing drift deluxe
10/23/13 16:53:27 : [11] "CXXXXXXXX" : thanks
10/23/13 16:53:41 : [11] "CXXXXXXXX" : i gtg now, cya later
10/23/13 16:53:47 : [13] "AXXXXXXXX" : bb
10/23/13 16:54:15 : [1] "SERVER-ADMIN" : BLUE player "DXXXXXXXX" crashed.

SERVLOG
10/23/13 18:58:48 : TAKE-OFF: Player id = [5], BLUE player "MXXXXXXXXXXXXXX" took off.
10/23/13 18:58:53 : LANDING: Player id = [15], BLUE player "DXXXXXXXXXXXXX" landed.
10/23/13 18:58:57 : SERVER:on_connect(7, 8X.XXX.30.101, 49971, "54XXXXXXXXXXX", "ecafd67bd7da5cd591eb2274dcb5e057")
10/23/13 18:59:01 : TAKE-OFF: Player id = [19], BLUE player "DXXXXXXXXXXXX" took off.
10/23/13 18:59:05 : Client [3] "fXXXXXXXXXX" joined Blue in "Su-27"(53)
10/23/13 18:59:09 : TAKE-OFF: Player id = [11], BLUE player "AXXXXXXXXXXX" took off.
10/23/13 18:59:14 : CRASH: Player id = [18], name = "= 36 = PXXXX (R)" crashed.
10/23/13 18:59:21 : LANDING: Player id = [16], BLUE player "MXXXXXXXX" landed.
10/23/13 18:59:22 : Disconnected client: [18] "= 36 = PXXXXX (R)"
10/23/13 18:59:28 : Disconnected client: [7] "54XXXXXXXXXXX"
10/23/13 18:59:28 : SERVER:on_connect(12, 3X.XX.159.100, 20138, "MXXXXXXXX", "76fba0f773ad927badae6447aa795ba9")
10/23/13 18:59:31 : TAKE-OFF: Player id = [16], BLUE player "MXXXXXXXX" took off.
CHATLOG
10/23/13 18:58:57 : [1] "SERVER-ADMIN" : "54XXXXXX" entered the game.
10/23/13 18:59:05 : [1] "SERVER-ADMIN" : "fXXXXXXX" joined BLUE in Su-27.
10/23/13 18:59:14 : [1] "SERVER-ADMIN" : BLUE player "= 36 = PXXXXX (R)" crashed.
10/23/13 18:59:28 : [1] "SERVER-ADMIN" : "MXXXXXX" entered the game.

Edited October 23, 2013 by sslechta
Additions

NineLine · October 24, 2013

Thank you. In the meanwhile, i will upload my latest latest version resaved with the mission editor of update 3, which is still on my local machine.

I will edit the first post of the thread where the mission is saved with the latest version, and will make a post in my thread noting the update.µ

kind regards,
Sven

Well that mission kicked the poop out of my system, not that my system is anything to write home about, I will see if I can have the devs use it for a test session to see if there is an issue in there or just so much going on...

For the record it crashed my game once after about 45 mins, and on the second run drove the FPS into the single digits after about an hour.

FlightControl · October 24, 2013

Well that mission kicked the poop out of my system, not that my system is anything to write home about, I will see if I can have the devs use it for a test session to see if there is an issue in there or just so much going on...

For the record it crashed my game once after about 45 mins, and on the second run drove the FPS into the single digits after about an hour.

hehe. So ED knows what to target for in next upgrades.

Running in medium quality does a lot. Just want to tell you. It is great fun!

Lots of stuff going on ... In the meanwhile, i've uploaded now the version 1.2.6.19532.

NineLine · October 24, 2013

hehe. So ED knows what to target for in next upgrades.
Running in medium quality does a lot. Just want to tell you. It is great fun!
Lots of stuff going on ... In the meanwhile, i've uploaded now the version 1.2.6.19532.

Oh for sure, it looks like a very fun complex mission for sure, not for the faint of heart.... hopefully someone at ED can confirm its ok, and there are no issues in there....

ENO · October 24, 2013

Here comes another... just like the other...

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: 1abf

Additional Information 4: 1abf2e1f4de1bcc9b5eb276334c52d8d

Sorry, wasn't there. Will try to get info.

crash 10.23.13.zip

Edited October 24, 2013 by ENO

Joyride · October 24, 2013

http://forums.eagle.ru/showthread.php?t=110990

So, run this mission for 2 hours in debug mode, and check if it crashes. And where...

Additional note:
I have done multiple changes in my mission. Note that i have ground troops, ships, and dynamic spawning of units. And anti ship missiles.
One thing to add: i've noticed that the effectiveness of antiship missiles have been greatly improved over the last releases. Since release 1.2.5 anti ship missiles were hardly effective. That has been fixed, thanks ed for that.

In the meanwhile, i am going to make subversions of this mission, and try to measure the effects of downsizing. F.e., only spawning one category without ground troops etc.

Sven

Ran this mission for a bit today. A few thoughts:

- I believe there is too much unnecessary AI action built in that may be causing stability and performance issues. For example, over 30 SA-10s in a tight area seems unnecessary. The miz spawns AI helos and unprotected aircraft which fly directly into and become fodder for the SA-10s, which can have a dozen missiles in the air at any time (serious hits on performance and opening the mission up to crashes, for only some "eye candy").

- while missions can often have 2,000+ units and be stable, MOVING groups create a much higher drain on sim resources, as well as missiles in the air tracking, AI aircraft, anything with waypoints! etc. I could just look into the mission editor and see you would have potential issues with this mission without even running it. Given the reality of DCS, economic mission design and tough decisions about "eye candy" vs. "mission essential" units and AI actions is a must, in my opinion.

- suggesting to potential mission downloaders that they should consider modifying their sim settings to be able to fly this .miz may significantly reduce the number who do download it! :-) Instead, I'd focus on giving the mission a diet and making it more playable (lean and mean!). Sounds like you are already working towards that...

karambiatos · October 24, 2013

sorry does anyone know how to open the .dmp files none of the non MS programs seem to detect them.

redfish · October 25, 2013

Crash Logs

Couple of crash logs.

CrashLogs.zip

NineLine · October 26, 2013

We ran the mission during a test session today, and I use the term ran loosely.... I think most everyone agrees with Joyride's findings, the mission needs to be cleaned up and thinned out a little...

Ran this mission for a bit today. A few thoughts:

- I believe there is too much unnecessary AI action built in that may be causing stability and performance issues. For example, over 30 SA-10s in a tight area seems unnecessary. The miz spawns AI helos and unprotected aircraft which fly directly into and become fodder for the SA-10s, which can have a dozen missiles in the air at any time (serious hits on performance and opening the mission up to crashes, for only some "eye candy").

- while missions can often have 2,000+ units and be stable, MOVING groups create a much higher drain on sim resources, as well as missiles in the air tracking, AI aircraft, anything with waypoints! etc. I could just look into the mission editor and see you would have potential issues with this mission without even running it. Given the reality of DCS, economic mission design and tough decisions about "eye candy" vs. "mission essential" units and AI actions is a must, in my opinion.

- suggesting to potential mission downloaders that they should consider modifying their sim settings to be able to fly this .miz may significantly reduce the number who do download it! :-) Instead, I'd focus on giving the mission a diet and making it more playable (lean and mean!). Sounds like you are already working towards that...

ENO · October 26, 2013

As soon as I saw 30 SA10s in his comments I figured I knew where that was going. However I also noted the points about eye candy and the impact it has on net performance and it has prompted me to go trim out the stuff that isn't directly mission orientated. I never had much- but enough that could jeopardize the performance of mission related AI movements...

Thanks guys

ENO · October 26, 2013

Seem to get this in this one mission of mine- about 2-3 hours in.

Problem signature:

Problem Event Name: AppHangB1

Application Name: DCS.exe

Application Version: 1.2.6.19532

Application Timestamp: 5260f1fc

Hang Signature: 0ffd

Hang Type: 0

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Hang Signature 1: 0ffdaf5c3fa405875ea423381d645680

Additional Hang Signature 2: 79b0

Additional Hang Signature 3: 79b071da4a2f5312dd8242b78415f721

Additional Hang Signature 4: 0ffd

Additional Hang Signature 5: 0ffdaf5c3fa405875ea423381d645680

Additional Hang Signature 6: 79b0

Additional Hang Signature 7: 79b071da4a2f5312dd8242b78415f721

Logs attached in a few minutes.

No crash log... but I have a funny feeling this one has something to do with something in a script error. So I'm doubtful this will be an ED issue... I passed on a note to Grimes because he said he was interested in the "error in error handling" issues that were occurring.

crash 10.26.13.zip

Edited October 26, 2013 by ENO

ENO · October 26, 2013

Problem signature:

Problem Event Name: APPCRASH

Application Name: dcs.exe

Application Version: 1.2.6.19532

Application Timestamp: 5260f1fc

Fault Module Name: AsyncNet.dll

Fault Module Version: 1.2.6.19532

Fault Module Timestamp: 5260f1f6

Exception Code: c0000005

Exception Offset: 000000000001f8fb

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1033

Additional Information 1: 0a03

Additional Information 2: 0a03c39457c3fb74988f7a9538433f4b

Additional Information 3: 6072

Additional Information 4: 6072851b2d985aa4af92e840edb17878

Another one... files attached soon.

crash 10.26.13a.zip

Edited October 26, 2013 by ENO

Wrecking Crew · October 26, 2013

This crash log comes from a Friday night. The game started lagging bad for clients and I quit. Don't know how much longer the Hollo Pointe server ran, but not much... Logs attached. This is from a stable mission, The Highway. Friday nights are typically laggy.

In addition there is this comment from a Client -

However I was frustrated by the SU-25t weapons. First the ability for a Tor or Tung to shoot down a kh-58 or MLU is pretty far fetched in my opinion. They stopped them from shooting down mavericks but not the much faster missles designed to kill them. So if you manage to shoot a missle that doesn't take down the server. Then you have to hope the missile makes to past the front of your plane without premature detonation. If all goes well from there and the missle manages to dodge the volley fire from the tors and tungs then you may get a sead kill.

WC

Edited October 26, 2013 by Wrecking Crew

redfish · October 27, 2013

Another Crash Log

One of the guys said that they were in the process of firing off a weapon - rocket.

Redfish

CrashLog.zip

1.2.6 Update 3 Server Crashes

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Recently Browsing 0 members