From: Roger Pack Date: 2009-01-25T05:35:33+09:00 Subject: [ruby-core:21548] Re: [Bug #744] memory leak in callcc? --001636458d88887d830461407916 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Mon, Jan 19, 2009 at 1:15 AM, Brent Roman wrote: > > Yuki and Roger, > > I'm glad to hear these patches are working out well for you. I assume that with 1.9 this style patch isn't as necessary as threads don't "share garbage" between each other--is that right? [each thread could still clean itself, but at least they don't share garbage between threads--is that right?] Also I might recommend renaming GC#limit to GC#malloc_limit or GC#alloc_limit since "limit" is somewhat ambiguous--is it a limit to the number of free pointers it will use? malloc size? [that type of thing]. Thanks so much! -=r --001636458d88887d830461407916 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Jan 19, 2009 at 1:15 AM, Brent Roman <brent@mbari.org&g= t; wrote:

Yuki and Roger,

I'= ;m glad to hear these patches are working out well for you.
 
I assume that with 1.9 this style patch isn't as necessary as thre= ads don't "share garbage" between each other--is that right? = [each thread could still clean itself, but at least they don't share ga= rbage between threads--is that right?]
 
Also I might recommend renaming GC#limit to GC#malloc_limit or GC#allo= c_limit since "limit" is somewhat ambiguous--is it a limit to the= number of free pointers it will use? malloc size? [that type of thing].
Thanks so much!
-=3Dr
 
--001636458d88887d830461407916--