Currently running Premiere to stabilize a video. Been running since last\nnight. It consumers 9gigs of "real memory" on a 12 gig machine.\n\nActivity monitor reveals:\n\nFree: 9 megabytes (aka: 0)\nWired: 1.12 gig\nActive: 7.26 gigs\nInactive: 3.62 gigs\n\n\n1- If a process is shown as using 9 gigs of ram, how come the "Active"\nis less ?\n\n2- How come the inactive isn't being trimmed back down since there is\nessentially 0 free RAM left and system paging quite a bit ?\n\n3- If a process makes use of say 1 gig of shared memory (code that is\nshared between processes for instance). Would that memory be billed to\n"Inactive" ? or would it be billed to each process that has a mapping to\nthis memory ? In the later case, adding all of the "real memory" units\nin Activity Monitor would result in more RAM being used than there is\nphysically installed.\n\nDoes "Inactive" contain common blocks of memory such as shared code and\nshared structures ? (this might explain why it isn't being trimmed down\nsince that code would be necessary). I was under the impression that it\nwas primarily a glorified cache of recently memory still considered\nvalid which could be remaopped toa process shoudl it need it. (for\ninstance, code from "mail.app" that can be remapped to a process\nstarting a new instance of mail.app). The way I read it, this was easily\ndisposable memory should there be a need for it.\n\n(This is on Snow Leopard BTW)\n\n\n(Additional note: Premiere seems to build something , increasing memory\nbig time and a couple hours later, back down to 2-3gigs of RAM and then\nstarts the buildup again). Its virtual memory seems stable at about 12 gigs.