![]() => Using container class UnpackStrategy::Dmg for /Users/markcastle/Library/Caches/Homebrew/downloads/aae6eaed841da059aa0fa12aa208ed3cba221ac0fa84bf8b3c0513058f456d2c-Disk Inventory X 1.2.dmg Hdiutil imageinfo /Users/markcastle/Library/Caches/Homebrew/downloads/aae6eaed841da059aa0fa12aa208ed3cba221ac0fa84bf8b3c0513058f456d2c-Disk\ Inventory\ X\ 1.2.dmg => Verifying SHA-256 checksum for Cask 'disk-inventory-x'. => Downloaded to -> /Users/markcastle/Library/Caches/Homebrew/downloads/aae6eaed841da059aa0fa12aa208ed3cba221ac0fa84bf8b3c0513058f456d2c-Disk Inventory X 1.2.dmg => /Users/markcastle/Library/Caches/Homebrew/downloads/aae6eaed841da059aa0fa12aa208ed3cba221ac0fa84bf8b3c0513058f456d2c-Disk Inventory X 1.2.dmg is quarantined => Verifying Gatekeeper status of /Users/markcastle/Library/Caches/Homebrew/downloads/aae6eaed841da059aa0fa12aa208ed3cba221ac0fa84bf8b3c0513058f456d2c-Disk Inventory X 1.2.dmg usr/bin/swift /usr/local/Homebrew/Library/Homebrew/cask/utils/quarantine.swift But, usually if there isn't enough RAM and it has to write it to the HD, a restart should clear that info from the HD and give me my space back like it usually does, wouldn't it? Right now there are 0 pageouts since I restarted the computer to stop the HD eating and still have 1.67 GB of ram free.īut, maybe one of the RAM sticks is going bad after 5 years now./usr/bin/curl -q -globoff -show-error -user-agent Mozilla/5.0\ \(Macintosh\ \ Intel\ Mac\ OS\ X\ 10_12_3\)\ AppleWebKit/602.4.8\ \(KHTML,\ like\ Gecko\)\ Version/10.0.3\ Safari/602.4.8 -location -silent -head -request GET \ Inventory\ X\ 1.2.dmgĪlready downloaded: /Users/markcastle/Library/Caches/Homebrew/downloads/aae6eaed841da059aa0fa12aa208ed3cba221ac0fa84bf8b3c0513058f456d2c-Disk Inventory X 1.2.dmg Next time it happens, I will follow your suggestions. My hunch is that it's RAM, the disappearing HDD space along with the unresponsive apps lead me to believe there's bad RAM, or something taking up far too much of it which cause excessive pageouts which would explain your missing HDD space. This should allow you to start narrowing down if it's a RAM or HDD issue. Before force-quitting Safari next time it beachballs, run the top command in Terminal again to see if it's a memory or processor issue, and check Activity Monitor to see how much RAM is being used and by which applications. ![]() Open Terminal, run "top", and check how many pageouts you have. If your HDD space is being eaten up there may be excessive pageouts (when your computer goes to access RAM but there isn't enough so it has to write that info to your HDD, thereby slowing down your whole system) that are supposed to be going to RAM but can't for some reason. Did you recently install new RAM? Switched RAM modules? Running a new app that is RAM intensive? How much RAM do you have? There may be a problem with your memory.
0 Comments
Leave a Reply. |