Recon Error

Bug #896143 reported by cranium
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
New
Medium
Unassigned

Bug Description

I'm experiencing alot of recons, been trying to track down the problem. But it has eluded me so far. It happens everytime i play online using xwis. So I Was wondering if one of the Devs could possibly take a look at the crashdump to determine whats causing this. Thanks in advance.

http://www.mediafire.com/?3j6b3l22xvnjp2z

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

Huh. Since when do recons cause crashdumps?

Revision history for this message
cranium (cranium) wrote :

I dont know, the ReconnectionError screen pops up, I click ok to quit and then it asks me if i want to create a crashdump.

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

Error - ConnectClass::Receive_Packet Queue full on PACKET_DATA_NOACK
Receive buffer overflow 1
Adding DATA_NOACK packet 3564 from 71.233.40.26 ; 0 ; 1488 to multicast queue
Error - ConnectClass::Receive_Packet Queue full on PACKET_DATA_NOACK
Receive buffer overflow 2

Seems to me like your game is throwing around too much data for the receiving buffers to handle... do you have the sync*.txt logs? Are there any specific circumstances where this happens?

Revision history for this message
cranium (cranium) wrote :

uploaded

No really specific time or event, just happens randomly, sometimes 2 min into game, sometimes 10 min into game.

But it happens in everygame

Revision history for this message
EVA-251 (eva-251) wrote :

What types of maps are you playing on?

During my testing sessions (I've uploaded 4 recons in a separate report), I noticed a (unsubstantiated) trend that maps with lots of garrisons were more prone to recons than others.
Battles on Invasion Confirmed and Let There Be Fight recon'd fairly quickly. On garrisonless Lost Lake, during same testing session, the battle was able to play out to the end.

Maybe it is just something on my end, as I removed every INI tag that stated a default value from every garrison (dont ask me about how long it took)

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

Well, I don't have any ideas on what could have caused this - something messed up the game's internal data and later the game crashed while trying to use them. It could have been corrupted seconds before the crash or minutes before, no real way to tell.

Revision history for this message
cranium (cranium) wrote :

Well crap. Alright I guess I'll have to somehow try to track it down. Though I have know idea of even where to begin, lol. Thanks DCoder, and even though we couldnt resolve this matter your help is most appreciative.

@EVA-251, yeah I was using a map with alot of garrisonable buildings, and even had my men garrison like 5 of them, but i dont see how that would cause a recon error?

Revision history for this message
YR M0ddEr (yr-m0dder) wrote :

Just a question, the people you play whith, do they also use Ares?

Revision history for this message
EVA-251 (eva-251) wrote :

@cranium- neither do I. It's just something I observed along with my testers, from test one with Ares SW branch. Mind you, it is also harder to reproduce, can't just conjure online-capable testers at any time. :S

@YR_M0ddEr- Trying to play Ares YR with a non-Ares using player results in an instant de-sync when both players finish loading. (as I found much to my embarrassment)

Revision history for this message
cranium (cranium) wrote :

I ran more tests, and i was able to garrison buildings witout incident, so i dont think that was an issue with my recons, though i still cant find out why the game crashes when someone wins or loses. It shows the You are victorious! screen and even announces You have won, then from there it crashes instead of going to the Score screen.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.