Re: Memory Leak-.dll problem

[Doug Donalson]

I am working on a simple test case for you, hnowever it is quite clear what
is happening.  Removing an action from a concurrent asynchronous schedule
does not release all of the memory.  That is the only case where it happens
and two independent simulations work with 2.0.1 standard and fail with the
new .dll's.
----- Original Message -----
From: Marcus G. Daniels <address@hidden>
To: <address@hidden>
Sent: Wednesday, March 08, 2000 4:17 PM
Subject: Re: Memory Leak-.dll problem


> >>>>> "D3" == Doug Donalson <address@hidden> writes:
>
> D3>   I have traced the memory leak to a problem in the updated 2.0.1
dll's.
> D3> It occurs when agents try to remove actions scheduled in the future,
ie a
> D3> birth event is scheduled but the agent is killed prior to the time the
> D3> action is scheduled.
>
> How about a self-contained test case to show the precise nature of
> this problem?  You seem to be suggesting that it is straightforward to
> reproduce the leak, but the absence of test case code says to me that
> maybe it is not.  I don't yet see the need for me to start guessing
> about this.
>
>
>
>                   ==================================
>    Swarm-Support is for discussion of the technical details of the day
>    to day usage of Swarm.  For list administration needs (esp.
>    [un]subscribing), please send a message to <address@hidden>
>    with "help" in the body of the message.
>


                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.