Re: Problem with memory leaks in Glade and GLADE

["Robert I. Eachus" <rieachus@attbi.com>]

Dr. Adrian Wrigley wrote:

> The Annex E server also consumes constantly rising memory.
> 
> In this case, each time a client partition connects and terminates,
> the server partition grabs roughly another 200kB of memory.
> My server code only allocates with "new" in one place, and
> calls "Unchecked_Deallocation" shortly after.
> I am puzzled by this, and suspect that the PCS may be leaking.
> Any suggestions for tracing and solving this problem?

The 200kB size makes me suspect that a task is being created and the 
memory not freed.  The issue may be that the task control block is not 
being freed after the task is terminated.  This can happen either as a 
bug in the implementation, or because the task may still be named after 
it is terminated.  I suspect a combination of the two.  A task created 
of a task type in an outer scope.  (When you exit the scope in which the 
task was created, it is still live, but you may not be able to name it. 
  When it terminates, the  TCB and the task stack can be cleaned up--but 
there is no way for the creator to clean up afterward.  And the task 
itself may not know that it can no longer be named.)

> Your thoughts?
> -- 
> Dr Adrian Wrigley, Cambridge, UK.
> 



-- 
                                                        Robert I. Eachus

Ryan gunned down the last of his third white wine and told himself it 
would all be over in a
few minutes.  One thing he'd learned from Operation Beatrix: This field 
work wasn't for him. --from Red Rabbit by Tom Clancy.