Modify

Ticket #997 (closed bug: fixed)

Opened 3 years ago

Last modified 2 years ago

Crash to desktop during multiplayer game

Reported by: fmbailey Owned by:
Priority: major Milestone: 2.3.0
Component: Engine: other Version: 2.2.4 (Unsupported!)
Keywords: movement Cc:
Blocked By: Blocking:
Operating System: Microsoft Windows

Description

For Version 2.2.4

Alright so I got the new game update, installed with no issues, booted it up fine and started up a multiplayer game with no issues. However after about an hour of gameplay the game crashes to the desktop. We were playing on the 8 player Cockate map. I had been mass producing Plasmite Flame Tanks on Treads and Tiger Bodies and sending them to attack.

My friend seemed to experience no crash and continued on to finish the round without a problem.

Attached is the crash report I got for this error.

Attachments

WZError224.txt (4.2 KB) - added by fmbailey 3 years ago.
fix997.diff (792 bytes) - added by Per 3 years ago.

Change History

Changed 3 years ago by fmbailey

comment:1 Changed 3 years ago by Per

  • Priority changed from major to critical
  • Keywords movement added
  • Version changed from unspecified to 2.2.4
  • Component changed from other to Engine: other
  • Milestone changed from unspecified to 2.2.5

comment:2 Changed 3 years ago by Zarel

Here's the line that crashed:

http://developer.wz2100.net/browser/tags/2.2.4/src/move.c#L3346

        if (terrainType(mapTile(map_coord(psDroid->pos.x), map_coord(psDroid->pos.y))) == TER_WATER)

It's most likely a crash for one of those functions (I see moveUpdateDroid doesn't check to see if psDroid is null, but it would've crashed earlier if it was).

(By the way, do you know what I like the most? Linux crash reports. Man, those are detailed.)

comment:3 Changed 3 years ago by Per

The problem is that the Y coordinate is too large, and so mapTile() returns NULL. I have made a mitigation for this problem to avoid a crash - attached. What I wonder about, though, is what this check in the code actually intends to accomplish.

Changed 3 years ago by Per

comment:4 Changed 3 years ago by Buginator

You going to apply the fix Per?

comment:5 Changed 3 years ago by Per

  • Status changed from new to closed
  • Resolution set to fixed

comment:6 Changed 3 years ago by Per

(In [8332]) Quick mitigation for crash reported in and that closes ticket:997

comment:7 Changed 2 years ago by Buginator

  • Milestone changed from 2.2.5 to 2.3

Milestone 2.2.5 deleted

View

Add a comment

Provide an email address (will not be publicly visible) in the Author field or register an account (uses your forum account).

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.