OpenEuphoria

RE: win32lib v0.57.4 Reply to matt

• Posted by Bernie Ryan <xotron at localnet.com> May 08, 2002
• 735 views

Matthew Lewis wrote:
> 
> 
> > -----Original Message-----
> > From: Bernie Ryan [mailto:xotron at localnet.com]
> 
> > I wonder how many of these memory leaks are being caused
> > by using that tk_mem.e through out the win32lib.
> > A think it would be wiser to let Rob's code and Windows
> > code to take care of the memory management. The
> > reason I say that is sometimes MS may change things
> > from one OS to the next and it may create memory
> > leaks that aren't be managed properly by the library.
> 
> tk_mem.e does use windows calls to manage memory.  The only thing it 
> adds is
> the concept of a 'memset', which allows for multiple 'frees' to be done 
> in
> one call by the user, so no more than you would expect using 
> allocate/free.
> These bugs seem to be resource leaks, which are slightly different.  
> It's
> not basic RAM that's been allocated and not freed, but resources that 
> have
> been created but not destroyed.
> 

Matt:
  The reason I think that allocating memory and by passing
  Rob's code is because when a program crashs Rob cleans
  up any memory that the program was using;
  But if you are allocating memory from the OS and your
  program crashs then you have no way of releasing that
  memory and I think that will evently require reboots
  and not make your users happy.
Bernie