On Jan 15, 2009, at 11:19 PM, Tobias Zimmerman wrote:
I am grateful to everyone who has responded, and, as I expected,
many concur
that VSIZE is a (largely) meaningless statistic. However, I am
still not
entirely satisfied with the answer to my first question, which is:
How does
the OS determine what to allocate for the VSIZE. One answer
suggested that
64-bit apps will receive 8GB, but I note that the Apache daemon
(httpd) runs
in 64-bit mode and is allocated on a few tens-of-megabytes (around
25MB per
instance on my machine). Is that because it does not have a GUI and
is not
written in Obj-C?
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
_______________________________________________
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
