Summary: *.lex files leaking memory
                 Project: Warzone Resurrection Project
            Submitted by: None
            Submitted on: Friday 10/26/2007 at 03:42 CEST
                Category: Engine: Scripting
                Severity: 4 - Important
                Priority: 5 - Normal
                  Status: None
             Assigned to: None
        Originator Email: [EMAIL PROTECTED]
             Open/Closed: Open
         Discussion Lock: Any
                 Release: svn/trunk
        Operating System: Microsoft Windows
         Planned Release: None



For the leaking *.lex files, it seems the best choice for this project would
be to recreate the memory pool/heap that was ripped out in favor of normal
malloc()/free() calls.  I am mainly talking about the scripting engine
though, not having a global memory pool as before.

I was looking at the mailing list, and it seems this was somewhat discussed
for awhile, but it seems it didn't go anywhere really.  It is hard to follow
some of the conversation on what is being said between some people, and some
heated debates. 

The main issue is that from looking at the orignal code, everything was done
with what is basically a garbage collector.  This solved all the issues with
the *.lex files leaking so much, since when the level ended, they could just
'free' the memory pool that they used.  It does no such thing now, as is
evident by all the leaking.

It really is pretty much a PITA to not have a gc while using bison/flex in
In C++, there are ways around it (use containers), but not really in C.

I am reporting this as a bug since it could be considered a unavoidable
bug/consequence of moving from a memory pool architecture to what is in place


Reply to this item at:


  Message sent via/by Gna!

Warzone-dev mailing list

Reply via email to