malloc errors / fragmentation?
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Thunderbird 2.0.0.17 (Macintosh/20080914) Back in May, Sean McBride wrote: Sometimes I see messages like: malloc: *** mmap(size=16883712) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug Can anyone point me at any guidelines, analysis tools, etc? Jay Levitt _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... and Eric Gouriou replied: I'd give vmmap a try and look for a VM fragmentation issue. I'm seeing the same thing on my 16GB Mac Pro (early 2008, OS X 10.5.5). I'm getting crashes every few days in WindowServer or coreservicesd; MenuMeters and Activity Monitor say I've got plenty of available RAM (either unused or idle). system.log says: system.log.0.bz2:Oct 29 14:35:19 macpro com.apple.coreservicesd[89]: coreservicesd(89,0xa0220fa0) malloc: *** mmap(size=16777216) failed (error code=12) system.log.0.bz2:Oct 29 14:35:19 macpro coreservicesd[89]: coreservicesd(89,0xa0220fa0) malloc: *** mmap(size=16777216) failed (error code=12)\n*** error: can't allocate region\n*** set a breakpoint in malloc_error_break to debug system.log.0.bz2:Oct 29 14:35:19 macpro com.apple.coreservicesd[89]: *** set a breakpoint in malloc_error_break to debug I've looked at vmmap, and while I get the gist of the output, I'm not sure what I should be looking for to see if the process's memory is fragmented. The -submap display shows plenty of small regions, but since I can't do a vmmap "right before I crash", I'm a little stumped... This email sent to site_archiver@lists.apple.com
participants (1)
-
Jay Levitt