# Park and others!.....Possible memory bug in Ruby? I'm stumped!

**URL:** <https://rubytalk.org/t/park-and-others-possible-memory-bug-in-ruby-im-stumped/178>\
**Category:** ruby-talk\
**Created:** [10 June 2002 03:38 UTC](https://rubytalk.org/t/park-and-others-possible-memory-bug-in-ruby-im-stumped/178 "2002-06-10T03:38:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kurt\_Euler1](https://avatars.discourse-cdn.com/v4/letter/k/d26b3c/32.png) [@Kurt\_Euler1](https://rubytalk.org/u/Kurt_Euler1)\
**Post date:** [10 June 2002 03:38 UTC](https://rubytalk.org/t/park-and-others-possible-memory-bug-in-ruby-im-stumped/178/1 "2002-06-10T03:38:18Z")

</div>

Hal-

Yes, you answered my question! Thanks!

-Kurt

> **···**
>
> -----Original Message-----  
> From: Hal E. Fulton [[mailto:hal9000@hypermetrics.com](mailto:hal9000@hypermetrics.com)]  
> Sent: Sunday, June 09, 2002 8:20 PM  
> To: [ruby-talk@ruby-lang.org](mailto:ruby-talk@ruby-lang.org)  
> Subject: Re: Park and others!..Possible memory bug in Ruby? I’m  
> stumped!
> 
> ----- Original Message -----  
> From: “Kurt Euler” [keuler@portal.com](mailto:keuler@portal.com)  
> To: “ruby-talk ML” [ruby-talk@ruby-lang.org](mailto:ruby-talk@ruby-lang.org)  
> Sent: Sunday, June 09, 2002 10:11 PM  
> Subject: RE: Park and others!..Possible memory bug in Ruby? I’m stumped!
> 
> > File.new(“./output/”+field[0],“w+”).write(content2)
> > 
> > Because an error occured here in one test, it appears that this  
> > line, like those before it, may also create an OS file. If this  
> > is true, is there way to rewrite THIS line to force a close the  
> > file during or just after the line executes? Or, perhaps  
> > immediate garbage collection occurs with this  
> > command, so I needn’t worry.
> 
> Kurt,
> 
> Not sure I understand all your constraints, since I haven’t  
> closely followed this thread.
> 
> But be aware that ‘open’ is essentially the same as ‘new’ except  
> that it can take a block. If it’s given a block, the file will  
> be closed after the block is executed.
> 
> File.open(“./output/#{field[0]}”, “w+”) { write(content2) }
> 
> # file is now closed
> 
> Does this help any?
> 
> By the way, my change to the file name is irrelevant… I just  
> wanted to illustrate a potentially clearer way of doing that  
> append.
> 
> Hal Fulton