#6201 - CTD on respawn

[GOPHUR]

It would be really good if those of you having this issue consistently could try doing the same on the beta. RAMP thinks he fixed this issue.

It still takes time to unload and load the world when you move locations but there shouldn't be a crash there now.

I did see one instance where I didn't get an AAR and that caused me not to be able to spawn but going back to the brigade fixed that.

[mrfancyp]

It would be really good if those of you having this issue consistently could try doing the same on the beta. RAMP thinks he fixed this issue.

It still takes time to unload and load the world when you move locations but there shouldn't be a crash there now.

I did see one instance where I didn't get an AAR and that caused me not to be able to spawn but going back to the brigade fixed that.

The problem is still there. Tested it yesterday two times (3 spawn and 15 spawn to CTD respectively) and once today (3 spawn to CTD).

[DOC]

As an aside for whatever it is worth, I get this almost everytime I change brigades. If I stay in a brigade and respawn on the same mission I just died on, I don't seem to sufffer it. If I jump around the UI chasing a new mission somwehere else, even if I go back to the original brigade and reselct that mission, I get CTD, no log file, nothing.

Game just closes down and departs from RAM.

Internal network ... from the office. My Cable has been down at home last few days so I haven't been able to test that route.

[timmy41]

I have about the same results as DOC, also I have recently noticed that the UI will lag for several seconds behind my clicks whenever this is about to happen.

[GOPHUR]

No need to report this anymore unless you get it in 1.34.6 beta or live.

If you'd like to see this fixed before the new year you'll need to try the beta and report back ASAP.

There is one known issue on the beta where your first sortie fails to give an AAR and you have to back out and reselect the weapon to spawn.

[mrfancyp]

CTD on respawn is still there in 1.34.6 beta. Did another test today using the beta playgate as described in the open test thread, CTD occured on 5th spawn.

[rubbish]

New host Tuesday afternoon with several improvements and fixes. Any improvement for you guys?

I am still getting this. Very long time on the loading screen followed by CTD or occasionally a spawn in.

Happens after switching brigades/country.

[Fri Dec 16 22:46:11.259 2011] spe

[Fri Dec 16 22:46:11.259 2011] t:11 sending pEx

[Fri Dec 16 22:46:11.551 2011] t:11 closing code:30014

[Fri Dec 16 22:46:11.901 2011] pmr

[Fri Dec 16 22:46:15.255 2011] redired

[Fri Dec 16 22:46:15.896 2011] t:3 pAcc

[Fri Dec 16 22:56:19.285 2011] t:3 pAcc

[Fri Dec 16 22:56:21.226 2011] tciRx ro:2 ip:0.0.0.144

[Fri Dec 16 22:56:21.228 2011] t:3 sNot

[Fri Dec 16 22:56:21.228 2011] rvj

[Fri Dec 16 22:56:21.632 2011] Netcode2:66.28.224.144 Opening 66.28.224.144...

[Fri Dec 16 22:56:21.632 2011] t:12 on:1 h:1109188752 p:27015 aCell

[Fri Dec 16 22:56:21.632 2011] ! cell active

[Fri Dec 16 22:56:21.951 2011] redired

[Fri Dec 16 22:56:22.108 2011] Netcode2:66.28.224.144 Opened

[Fri Dec 16 22:57:09.572 2011] t:3 closing code:30016

[Fri Dec 16 22:57:09.572 2011] t:3 got ENOTCONN:126

[Fri Dec 16 22:57:09.574 2011] t:3 closing code:30016

[Fri Dec 16 22:57:09.574 2011] t:4 closing code:30016

[Fri Dec 16 22:57:09.574 2011] t:4 got ENOTCONN:126

[Fri Dec 16 22:57:09.574 2011] t:12 closing code:30016

[Fri Dec 16 22:57:09.574 2011] t:12 got ENOTCONN:126

[Fri Dec 16 22:57:09.574 2011] Lost connection to cell host connection error (#12): 126 - Not connected

[Fri Dec 16 22:57:09.975 2011] Netcode2:66.28.224.144 Disconnecting

[Fri Dec 16 22:57:09.983 2011] Netcode2:66.28.224.144 Opening 66.28.224.144...

[Fri Dec 16 22:57:09.983 2011] t:13 on:1 h:1109188752 p:27015 aCell

[Fri Dec 16 22:57:09.983 2011] ! cell active

Date and time: 12/16/2011 22:58:22

Program compile time: Nov 23 2011 16:19:25

File version: 1.34.5

GL Vendor: NVIDIA Corporation

Renderer: GeForce GTX 285/PCI/SSE2

Access violation: Illegal read by 0088C57C at 00000008

OS-Version: 6.1.7601 (Service Pack 1) 0x100-0x1

[0088C57C] (ww2): :

Edited December 16, 2011 by Rubbish

[kc25x]

Still happening on death/brigade/persona change

[mrfancyp]

This problem actually got worse for me the last few days on the live server. I get a CTD after every 2. or 3. spawn now.

[stoves9]

I get a ctd on 2nd or 3rd respawn too.

[shmonkey]

I CTD everytime I respawn

[GOPHUR]

I can't release the fix because no one has tested it.

*ahem*

See sticky for 1.34.6 test please!

[GOPHUR]

Bump. Need testing TODAY if I want top release this week. If not this week then After the new year's.

[mrfancyp]

I tested it and posted in the other (sticky) thread. Not sure what you need - multiple tests, more info per test or corroboration of results from other people?

[GOPHUR]

TYS I'll take a look.

[bagir]

As an aside for whatever it is worth, I get this almost everytime I change brigades. If I stay in a brigade and respawn on the same mission I just died on, I don't seem to sufffer it. If I jump around the UI chasing a new mission somwehere else, even if I go back to the original brigade and reselct that mission, I get CTD, no log file, nothing.

Game just closes down and departs from RAM.

Internal network ... from the office. My Cable has been down at home last few days so I haven't been able to test that route.

1. Mostly did not got CTD if I spawning in the towns that lie in the south part of the map. So CTD depends on town.

2. Mostly did not got CTD even if change brigade, but spawn on the FB. No loading stuctures, buildings, and as result textures around me - no CTD.

3. Mostly did not got CTD even if change brigade and spawn in the same town (where fought just before). Structures, buildings, and as result textures around me yet in RAM.

P.S. After CTD saw on runned in background 'connection monitor' that show - last 10-20 sec nothing received from server (it look like transfer disconected from moment when town and textures should be began loading).

Edited December 23, 2011 by bagir

[Redwing]

Havent had a CTD yet since patch

when killed or move to new mission load time is still high like it was going to crash

rtb respawns alot faster load in

[mrfancyp]

I still get this with the current version.

[raptor]

Yeah, I'm still getting it too.

WinXP

[GOPHUR]

Explain what you get and include your logs for me. This bug is fixed so you're getting something else.

[mrfancyp]

Explain what you get

Exactly the same bug described above in this thread. Sometimes the game CTDs without the long loading time before spawning. Other times I get that long 30-40 second loading time before the client gives up.

and include your logs for me.

This is the last part of my log, can't post the entire thing as it is too long:

[Tue Jan 03 22:02:35.893 2012] spe

[Tue Jan 03 22:02:35.893 2012] t:21 sending pEx with result: 27

[Tue Jan 03 22:02:36.430 2012] t:21 closing code:30006

[Tue Jan 03 22:02:36.430 2012] t:21 got ENOTCONN:10057

[Tue Jan 03 22:02:36.430 2012] t:21 closing code:30122

[Tue Jan 03 22:02:36.848 2012] pmr

[Tue Jan 03 22:02:37.287 2012] t:22 closing code:30122

[Tue Jan 03 22:02:37.287 2012] spe

[Tue Jan 03 22:02:37.287 2012] pEx/no cell

[Tue Jan 03 22:02:41.912 2012] t:3 pDen

[Tue Jan 03 22:03:50.187 2012] t:3 pAcc

[Tue Jan 03 22:03:51.146 2012] tciRx ro:2 ip:0.0.0.144

[Tue Jan 03 22:03:51.231 2012] t:3 sNot

[Tue Jan 03 22:03:51.231 2012] rvj

[Tue Jan 03 22:03:51.637 2012] tciNoCnx

[Tue Jan 03 22:03:52.82 2012] Netcode2:209.144.109.144 Opening 209.144.109.144...

[Tue Jan 03 22:03:52.082 2012] t:23 on:1 h:3515903376 p:27015 aCell

[Tue Jan 03 22:03:52.082 2012] ! cell active

[Tue Jan 03 22:03:52.469 2012] redired

Date and time: 1/3/2012 22:04:37

Program compile time: Dec 12 2011 10:19:10

File version: 1.34.7

GL Vendor: ATI Technologies Inc.

Renderer: AMD Radeon HD 6900 Series

Access violation: Illegal read by 0063E100 at 00000058

This bug is fixed so you're getting something else.

Don't you have an auto-report tool for CTDs? If I'm the only person getting this bug then I can understand how it wouldn't be worth your time, but I think the issue is that I and a few other players just follow a play style which is not as common and that therefore the bug is not reported very often (likelihood of CTD increases with number of spawns. People guarding FBs or CPs spawn at one place, then spawn somewhere else until the game crashes. People who spawn a plane and fly around for 2 hours per sortie might never see this bug).

[Memoi]

I'm having this problem too.

Had it during the 1.34 testing, hence the lack of me playing over recent months.

My first mission, spawned in as normal, despawned then went to spawn again resulting in a CTD.

[Thu Jan 05 12:42:41.810 2012] t:0 closing code:30100

[Thu Jan 05 12:42:42.676 2012] t:1 closing code:30006

[Thu Jan 05 12:42:43.523 2012] t:2 closing code:30006

Thu Jan 05 12:42:43 2012 network election of 2 addresses: 66.28.224.143:614ms. 209.144.109.143:596ms. Winner: 209.144.109.143, Manual Selection: 66.28.224.143

[Thu Jan 05 12:42:44.140 2012] t:3 srvInf

[Thu Jan 05 12:42:44.481 2012] t:3 on:1 h:1109188751 p:27015 aMap

[Thu Jan 05 12:45:07.534 2012] t:3 pAcc

[Thu Jan 05 12:45:11.356 2012] tciRx ro:2 ip:0.0.0.144

[Thu Jan 05 12:45:11.382 2012] t:3 sNot

[Thu Jan 05 12:45:11.382 2012] ! no cell for rvj

[Thu Jan 05 12:45:11.753 2012] tciNoCnx

[Thu Jan 05 12:45:12.100 2012] Netcode2:66.28.224.144 Opening 66.28.224.144...

[Thu Jan 05 12:45:12.100 2012] t:5 on:1 h:1109188752 p:27015 aCell

[Thu Jan 05 12:45:12.429 2012] redired

[Thu Jan 05 12:45:12.600 2012] Netcode2:66.28.224.144 Opened

[Thu Jan 05 12:45:15.887 2012] Netcode2:66.28.224.144 Established

[Thu Jan 05 13:15:56.567 2012] Netcode2:66.28.224.144 Disconnecting

[Thu Jan 05 13:15:56.567 2012] Netcode2:66.28.224.144 Max bps: 0.00 in, 0.00 out

[Thu Jan 05 13:15:56.567 2012] Netcode2:66.28.224.144 Session Statistics:

Actual bytes per second sent 1136

Actual bytes per second received 5888

Message bytes per second sent 740

Message bytes per second resent 74

Message bytes per second queued 740

Message bytes per second processed 5475

Message bytes per second ignored 571

Total bytes sent 1905613

Total bytes received 12956981

Total message bytes sent 1205414

Total message bytes resent 670

Total message bytes queued 1205414

Total message bytes received 12210156

Total message bytes ignored 2307

Messages in send buffer, by priority 0,0,0,0

Bytes in send buffer, by priority 0,0,0,0

Messages in resend buffer 2

Bytes in resend buffer 148

Current packetloss 0%

Average packetloss 0%

Elapsed connection time in seconds 1844

[Thu Jan 05 13:15:56.567 2012] spe

[Thu Jan 05 13:15:56.567 2012] t:5 sending pEx with result: 27

[Thu Jan 05 13:15:56.895 2012] t:5 closing code:30006

[Thu Jan 05 13:15:56.895 2012] t:5 got ENOTCONN:10057

[Thu Jan 05 13:15:56.895 2012] t:5 closing code:30122

[Thu Jan 05 13:15:57.222 2012] pmr

[Thu Jan 05 13:15:57.677 2012] t:6 closing code:30122

[Thu Jan 05 13:15:57.677 2012] spe

[Thu Jan 05 13:15:57.677 2012] pEx/no cell

[Thu Jan 05 13:29:19.423 2012] t:3 pAcc

[Thu Jan 05 13:29:19.946 2012] t:3 pDen

[Thu Jan 05 13:29:40.019 2012] t:3 pAcc

[GOPHUR]

Yeah we auto report if the game exits and gives a code.

Access violation: Illegal read by 0063E100 at 00000058

This is the part we're most interested in. We've had 236 of those posted since 1.34.7 went live. It's number four on our list of crashes. In the grand scheme of things that's enough to be worthy of a fix but it isn't critical.

What I'd like to know is if this is the crash you get every time or are you getting several errors. That could help point us to a source of the issue.

[mrfancyp]

Ok, I'll keep an eye out for those error codes. Here are my last two:

Access violation: Illegal read by 0063E100 at 00000058

Access violation: Illegal write by 008C3707 at 00000000

[bigrow]

I haven't had a chance to do any serious testing on this, but something happened last night that i thought might be worth reporting......

I have started running 2 accounts again now i have a new gfx card.

Last night i had been running just 1 account for 1 hour. I then logged my second account in and spawned at a new location away from main account. Spawn time was very quick(1-2 seconds). I then, straight away, moved my main account to the same location(it had been in a busier area) and spawn in took over 20 seconds. Respawning both accounts at the same location was very quick.

I have 0 coding/system resource management experience, but it seems odd to me that only the account that had been spawned elsewhere suffered this long delay.

fwiw..

i5 2500k @4ghz

8gb ram

gtx560

win7 64