On 12/2/09 12:33 PM, Jens Alfke said: >> I'm stress testing a 64 bit GC app with AUTO_USE_GUARDS and left it >> running overnight. This morning it's crashed here: > >Doesn't that turn on GuardMalloc, which adds an extra unmapped page >before and after every allocation? In other words, there's an extra 8k >of address space used up by every single malloc call. This isn't going >to show up as RAM used by the process, because it's not mapped to >anything, but it certainly chews up address space in a hurry.
Thanks to all for your replies. If GC memory is really limited to 8 GB (and not 32), then I probably am hitting that limit with the guard pages on. :( Is there a way to increase that limit, at least in debug? 8 is pretty puny. :( And Jens, AUTO_USE_GUARDS is the same principle as Guard Malloc, but they are not identical. As I understand it, the former applies to memory in the GC zone, the latter to the malloc zone. In my app anyway, AUTO_USE_GUARDS is slow, GuardMalloc is slower, and with them both on it's very slow indeed. -- ____________________________________________________________ Sean McBride, B. Eng s...@rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
