• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: What Determines VSIZE allocation?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What Determines VSIZE allocation?


  • Subject: Re: What Determines VSIZE allocation?
  • From: "Tobias Zimmerman" <email@hidden>
  • Date: Fri, 16 Jan 2009 01:26:53 -0500

>
> I believe, if I understood Bill Bumgarner's message correctly, is that
> the 8GB range being assigned to the app is due in part to the design
> of the garbage collector, libauto. I doubt that Apache is compiled to
> use the garbage collector at all and thus, is not having that memory
> range allocated to it.
>
> > If the outsized VSIZE does indicate "misbehavior in [my] process",
> > what are
> > the types of things I should look for?  I don't have any memory
> > leaks (that
> > I can see -- the app runs for hours without increasing its memory
> > consumption, and nothing obvious appears in instruments).  I am not
> > creating
> > hundreds of objects, and I have a limited number of classes in my app.
>
> As I understand it, it's not the size of the VSIZE that should concern
> you, but rather if the size only ever increases. In that case you may
> have files mapped to memory that you are leaking. Perhaps there are
> other conditions that would cause this, but that seems the most likely.
>
>
> Ashley
>
>
> ------------------------------
>
First, apologies for messing up the subject on my previous reply.  Thanks
for getting back to me anyway.
Yes, I overlooked Bill Bumgarner's reference to the GC.  Turning off GC in
my app does indeed reduce VSIZE from 8GB to 350MB (of course, since I wrote
it strictly as a GC app, it doesn't actually work without GC, but that's my
fault :)

So, moral of the story: GC apps in 64-bit mode allocate themselves a
tremendous amount of virtual memory, but unless they are actually *using* a
lot of VM, then there is nothing to worry about.  Did I get that right?
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: What Determines VSIZE allocation?
      • From: Bill Bumgarner <email@hidden>
  • Prev by Date: Re: Cocoa-dev Digest, Vol 6, Issue 86
  • Next by Date: Re: What Determines VSIZE allocation?
  • Previous by thread: Re: What determines VSIZE allocation?
  • Next by thread: Re: What Determines VSIZE allocation?
  • Index(es):
    • Date
    • Thread