Re: Memory problem with latest malloc.c

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Joe Marcus Clarke <marcus@...>
Cc: current <current@...>
Date: Wednesday, January 2, 2008 - 10:26 pm

Joe Marcus Clarke wrote:

Revision 1.160 of malloc.c uses sbrk instead of mmap by default.  The 
intent is to make data segment resource limits useful.  So, there are 
two possible explanations I can think of for your problems.  The first 
possibility is that there is still a bug in malloc that you're hitting. 
  However, the other possibility is that the python program you're 
running really needs more than 512 MB of memory, and you're hitting the 
resource limit.

It would be really helpful to me if you run your program with 
MALLOC_OPTIONS=dM and monitor memory usage.  These flags cause mmap to 
be used instead of sbrk, and we can find out from that how much memory 
you really need.  If peak memory usage is substantially different when 
using mmap versus sbrk, there's probably a malloc bug.

This latest round of malloc changes hasn't been much fun.  Thanks for 
your help and patience.

Jason
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Memory problem with latest malloc.c, Joe Marcus Clarke, (Wed Jan 2, 6:49 pm)
Re: Memory problem with latest malloc.c, Ivan Voras, (Thu Jan 3, 6:27 am)
Re: Memory problem with latest malloc.c, Jason Evans, (Wed Jan 2, 10:26 pm)
Re: Memory problem with latest malloc.c, Joe Marcus Clarke, (Thu Jan 3, 2:00 am)
Re: Memory problem with latest malloc.c, Jason Evans, (Thu Jan 3, 2:12 am)
Re: Memory problem with latest malloc.c, Joe Marcus Clarke, (Thu Jan 3, 2:15 am)