# Initializing and destroying(?) instance variables

**URL:** <https://www.ruby-forum.com/t/initializing-and-destroying-instance-variables/116729>\
**Category:** Ruby\
**Created:** [October 9, 2007, 3:51am UTC](https://www.ruby-forum.com/t/initializing-and-destroying-instance-variables/116729 "2007-10-09T03:51:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mr\_tibs](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/439d5e/32.png) [@mr\_tibs](https://www.ruby-forum.com/u/mr_tibs)\
**Post date:** [October 9, 2007, 3:51am UTC](https://www.ruby-forum.com/t/initializing-and-destroying-instance-variables/116729/1 "2007-10-09T03:51:24Z")

</div>

Hi,

I finished writing a fairly large Ruby application and I was careless  
with cleaning up variables. My objects contain references to large  
ActiveRecord objects (instance variables), and I wanted to make sure  
that I don’t specifically need to set these instance variables to nil  
when they’re not used anymore: as long as I set the parent object to  
nil, since there will be no reference to its instance variables, the  
parent object and its instance variables (objects) should be removed  
by the GC. Is this correct?

For example, I might have this program:

class Blah

attr\_accessor :arr

def initialize  
@arr = Array.new(10000000, ‘TEST’)  
end

end

while (true)  
b = Blah.new  
sleep 5  
end

I noticed that the memory on my machine only goes up at the beginning  
of the program, and then stays constant. I can only conclude that each  
time the loop executes, the old b.arr becomes unreferenced and is  
garbage collected and that the new b.arr is allocated (thus memory  
usage is the same).  
I just need someone to confirm this, since my program freezes after  
running more than 24hours and I can’t find the (memory) leakage.

Thanks,  
Tiberiu