[Warzone-dev] back to back runs leaks results.

This back to back runs of skirmish game default map, default players. (you need patch to be able to run back to back MP games, I sent that last week, not commited yet) If you compare before message, you see double the allocations. If run 3 times, then it will triple amount. BYTE SIZE: 2

[Warzone-dev] leaks & patches

Looks like flex files leak, this is from run skirmish, 4p, quit as soon as you see base, then quit out of program. Also script_parser.y and so on leak. It no look like any cleanup is done. Also, any plans to commit patches waiting on mailing list sometime this week? This small sample of mem

[Warzone-dev] [bug #9413] ctd: start of beta campaign*** continue game after transport leaves alpha base = ctd

URL: Summary: ctd: start of beta campaign*** continue game after transport leaves alpha base = ctd Project: Warzone Resurrection Project Submitted by: hellangel_666 Submitted on: Thursday 06/28/2007 at 21:08

Re: [Warzone-dev] dangling pointer problem

I noticed some of CHECK_PROJECTILE/CHECK_OBJECT are unnecessary and give false alerts,because most of the time the functions should be able to figure out the objects who are marked as 'died' and will be GC'ed next frame,just did a 7 AI with slider maxed out run for few hours in MSVC(to make igno

[Warzone-dev] [bug #9410] crashes in campaign - trunk version r1629

URL: Summary: crashes in campaign - trunk version r1629 Project: Warzone Resurrection Project Submitted by: None Submitted on: Thursday 06/28/2007 at 16:37 CEST Category: None S

Re: [Warzone-dev] [patch]Re: displayBufferSize &DisplayBuffer ?

On Thu, 28 Jun 2007 02:43:45 -0400 [EMAIL PROTECTED] wrote: >After looking at code, best thing to **NOT** do away with >GeneralBuffer. (displaybuffer). >Reason is there are ~628 calls to load into this buffer. >Now we have 1 malloc, and 1 free, so that is tons less malloc/free > >calls we no hav