Jump to content
6 posts in this topic

Recommended Posts

If the OS thinks there's memory at, say, 2 GB, it may try to write there. When it does, there won't be any chips there, and at best the kernel will panic. At worst, the system will simply hang forever waiting for an ACK line to be asserted. Trust me, this is a major issue.

  • 2 months later...

I have since discovered that this seems to be a bug in System Profiler and that the OS actually has a correct view of how much memory I have. Running "top" in a terminal window yields:

 

Processes: 56 total, 2 running, 54 sleeping... 179 threads 19:06:58

Load Avg: 0.13, 0.11, 0.07 CPU usage: 6.6% user, 5.7% sys, 87.7% idle

SharedLibs: num = 136, resident = 33.2M code, 4.46M data, 7.38M LinkEdit

MemRegions: num = 6628, resident = 178M + 19.4M private, 117M shared

PhysMem: 91.6M wired, 159M active, 294M inactive, 545M used, 478M free

VM: 9.21G + 88.1M 27955(2) pageins, 0(0) pageouts

 

Note that the PhysMem stats seem to be correct for a 1 GB memory stick.

 

iStat Pro gives similar numbers, so I'm fairly confident that everything's okay.

×
×
  • Create New...