View Issue Details

IDProjectCategoryView StatusLast Update
0004400Spring engineGeneralpublic2014-05-22 00:00
ReporterMajorBoredom Assigned Toabma  
PrioritynormalSeveritycrashReproducibilitysometimes
Status closedResolutionunable to reproduce 
Product Version96.0.1+git 
Summary0004400: Crash ingame on UDPConnection operations
DescriptionThis crash occurs fairly frequently. It may be due to code that I have on my libunwind feature branch, but I cannot see anything that would interfere with network code at all.

The crash usually happens inside the UDPConnection::SendIfNecessary() or UDPConnection::Flush() functions, but is not restricted to outgoing packet operations. For example, I have also seen similar issues with ProcessRawPacket().
Steps To ReproduceI get this bug in about 30% of the BA games that I play. I find that it happens more in larger games where there is generally more network traffic. It started happening as I work on the libunwind feature branch. I also did a kernel update recently but I can't imagine how that would interfere.
Additional InformationI have several stack traces of this bug, some produced with gdb and some produced with libunwind. It consistently happens with the UDPConnection class and usually involves corrupt containers but I have also seen failed assertions that arise from i.e.: badly numbered packets. It is related to 0004396.
TagsNo tags attached.
Attached Files
udpconnflush-backtrace.1.txt (Attachment missing)
udpconnflush-backtrace.2.txt (Attachment missing)
udpconnflush-infolog.txt (Attachment missing)
udpconnupdate-backtrace.1.txt (Attachment missing)
Checked infolog.txt for Errors

Activities

Issue History

Date Modified Username Field Change
2014-05-21 22:33 MajorBoredom New Issue
2014-05-21 22:33 MajorBoredom File Added: udpconnflush-backtrace.1.txt
2014-05-21 22:33 MajorBoredom File Added: udpconnflush-backtrace.2.txt
2014-05-21 22:33 MajorBoredom File Added: udpconnflush-infolog.txt
2014-05-21 22:33 MajorBoredom File Added: udpconnupdate-backtrace.1.txt
2014-05-22 00:00 abma Status new => closed
2014-05-22 00:00 abma Assigned To => abma
2014-05-22 00:00 abma Resolution open => unable to reproduce