Where does the memory go?

[Richard Gaskin]

Dennis Brown wrote:
>> Another way to ask that question would be to pose it as its  
>> corollary: do we have evidence of memory leaks in Rev?
>>
>> There may be, but it seems not too difficult to test:  make a  project 
>> that adds and deletes large sets of custom props and  objects 
>> containing large amounts of data, check the memory usage  before it 
>> starts, let it run all night, and check it again in the  morning.
> 
> I did just that.  I made a button with the following quickly thrown  
> together script and ran it, stopping it every so often to save the  
> stack and check the size.  The good news is that the rather large set  
> of properties and data (210MB) was created and deleted each pass  (only 
> took a few seconds per pass) resulted in not even a single byte  change 
> in stack size between passes.  Thanks for the suggestion.  Now  I can 
> sleep tonight!

FWIW, for card deletion there is sometimes some space leftover as a 
result of the hashing scheme used, much as there would be for record 
deletion in most databases.  This can be reclaimed with the compact 
command -- from the Dictionary entry for "compact":

    When you cut or delete a card, some free space is left
    within the stack. This empty space is reclaimed when
    you choose File menu Save. Use the compact command to
    reclaim this empty space without having to save the stack.


--
  Richard Gaskin
  Managing Editor, revJournal
  _______________________________________________________
  Rev tips, tutorials and more: http://www.revJournal.com