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"
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 007/196] Chinese: add translation of stable_kernel_rules.txt |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
git: | |
| Alexey Dobriyan | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [BUG] New Kernel Bugs |
