From: Dossy <dossy@...>
Date: 2002-06-10T05:53:43+09:00
Subject: Re: Park and Sean....Possible memory bug in Ruby? I'm stumped!

On 2002.06.10, Wesley J Landaker <wjl@icecavern.net> wrote:
> The first one creates a file object, does a read, then the file object 
> is floating. If and when it gets garbage collected, the file will be 
> closed. But if you run a ton of these commands in a row, it's extremely 
> easy to open more files than is allowed by the OS before the garbage 
> collector ever kicks in. (Perhaps ruby ought to catch the error and run 
> the garbage collector, then try again transparently?)

You know, this might be the problem I'm experiencing with DBI and
dbd_oracle.

I never execute StatementHandle#finish -- could I be running out of
statement handles?  (Remember, when I explicitly added "GC.start"
to my code, the crash went away.)

Shouldn't DBI tell me I've run out of statement handles, rather than
segfaulting Ruby?

Maybe I can create a reproducible test case now, if this is why it's
dying ...

-- Dossy

-- 
Dossy Shiobara                       mail: dossy@panoptic.com 
Panoptic Computer Network             web: http://www.panoptic.com/ 
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)