Re: [gecode-users] Memory problem

2008-08-28 Thread Gustavo Gutierrez
gt; > Cheers > > Christian > > > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Gustavo Gutierrez > *Sent:* Thursday, August 28, 2008 7:44 AM > *To:* Christian Schulte > *Cc:* [EMAIL PROTECTED] > *Subject:* Re: [gecode-users] Memory

Re: [gecode-users] Memory problem

2008-08-28 Thread Christian Schulte
ailto:[EMAIL PROTECTED] Sent: Thursday, August 28, 2008 1:06 PM To: Gustavo Gutierrez Cc: [EMAIL PROTECTED]; Christian Schulte Subject: Re: [gecode-users] Memory problem Gustavo Gutierrez wrote: On Thu, Aug 28, 2008 at 9:20 AM, Guido Tack <[EMAIL PROTECTED]> wrote: I tried to find out

Re: [gecode-users] Memory problem

2008-08-28 Thread Guido Tack
Gustavo Gutierrez wrote: On Thu, Aug 28, 2008 at 9:20 AM, Guido Tack <[EMAIL PROTECTED]> wrote: I tried to find out more about the Mac OS malloc. Apparently, Mac OS never frees blocks that are smaller than 15359 bytes, but rather tries to reuse them for further mallocs in the same process.

Re: [gecode-users] Memory problem

2008-08-28 Thread Gustavo Gutierrez
On Thu, Aug 28, 2008 at 9:20 AM, Guido Tack <[EMAIL PROTECTED]> wrote: > I tried to find out more about the Mac OS malloc. > > Apparently, Mac OS never frees blocks that are smaller than 15359 bytes, > but rather tries to reuse them for further mallocs in the same process. > http://kevin.sb.org/20

Re: [gecode-users] Memory problem

2008-08-28 Thread Guido Tack
I tried to find out more about the Mac OS malloc. Apparently, Mac OS never frees blocks that are smaller than 15359 bytes, but rather tries to reuse them for further mallocs in the same process. http://kevin.sb.org/2007/07/05/malloc-free-space-not-reclaimed/ I tried replacing malloc with ptma

Re: [gecode-users] Memory problem

2008-08-28 Thread Christian Schulte
for Gecode as well. Cheers Christian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gustavo Gutierrez Sent: Thursday, August 28, 2008 7:44 AM To: Christian Schulte Cc: [EMAIL PROTECTED] Subject: Re: [gecode-users] Memory problem On Wed, Aug 27, 2008 at 11:10 AM

Re: [gecode-users] Memory problem

2008-08-27 Thread Guido Tack
Gustavo Gutierrez wrote: > After trying the same problem occurs. Is there a way to instrument > gecode to use a different allocator for memory?, i mean, something > similar to STL in which many of the data structures provided take an > optional allocator template parameter. All allocation in

Re: [gecode-users] Memory problem

2008-08-27 Thread Gustavo Gutierrez
i mean, something similar to STL in which many of the data structures provided take an optional allocator template parameter. Regards, Gustavo *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Gustavo Gutierrez > *Sent:* Wednesday, August 27, 2008 10:56 AM > *To:* [

Re: [gecode-users] Memory problem

2008-08-27 Thread Christian Schulte
] [mailto:[EMAIL PROTECTED] On Behalf Of Gustavo Gutierrez Sent: Wednesday, August 27, 2008 10:56 AM To: [EMAIL PROTECTED] Subject: [gecode-users] Memory problem Hi All, Some time ago someone reported an strange memory behavior in mac os x on the gecode list. I do not know whether it was fixed

[gecode-users] Memory problem

2008-08-27 Thread Gustavo Gutierrez
Hi All, Some time ago someone reported an strange memory behavior in mac os x on the gecode list. I do not know whether it was fixed but i think it still remains in the current implementation. The problem apparently happens only in mac os x. You can get it by replacing the main function of the que