Leopard: Repair Permissions - Installdb - massive memory usage!
It's been known for a while now that the disc utility isn't running up to snuff on leopard. There was a recent update that now allows the time-bar to run, showing you how long you have to wait 'till done (which was definitely a fix from there being no time-bar at all). However, I'm finding a very strange thing occurs when I try to repair permissions.
Simultaneously as I tried repairing, I ran the activity monitor to see what the processes looked like on my ram (I'm operating on 512, which I know is a bit low for the new OS). What I found was that there's a process name called installdb, that was going haywire. When I began to repair the permissions, the installdb process was using less than a dozen mb of ram, within minutes my cpu was heating up super-fast, and I found this installdb was sucking up more and more ram, until finally the process shut down (of its own accord?) at 220 MB of ram used.
Of course my page in-out count got super high at that point because I'm only using 512 to begin with, but I just have to think that something in the installdb process is responsible for the difficult times with disc repair.
As well, while the new update solved one particular permission issue (already discussed, SUID file), it seems to have left many more in its wake. I get the following list of messages now from repair disc, and this list has not changed, despite having repaired permissions 3 times in the last 2 days.
Anyone have a heads up on either the installdb process, or the below-listed repair issues?
Permission repair issues:
Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Thanks a ton,
ZenChess
PS: I notice that after the permissions repair was complete, my activity monitor went from an average of 230 MB's of free ram, to 305. So it looks like the repair permissions did have an effect, although the messages left behind said no repairs went into effect.
Totally confused,
ZenChess
Similar Messages
-
Massive memory usage when using latest version of final cut, 10 minutes after restart.
Hey I am really struggling with using Final Cut Pro X and I suspect there is some software issue.
I am editing a one minute video clip, the video files are 1080 h264. I restart my computer and only open final cut. After 10 minutes of editing I cant barely navigate my computer anymore as it is going so slow, until eventually I have to force reboot my computer. I can scarcly export anything out of final cut, when I do my computer feels like its about to die and if it exports I seem to get broken frames and/or missing media.
I reinstalled my mac only about 2 months ago.
System specs.
Mac book pro.
13-inch, Late 2011
Processor 2.4 GHz Intel Core i5
Memory 4 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 384 MB
On my previous mac book pro (early 2010, 4 gm ram), running snow leopard and previous versions of final cut I was able to edit 3, 1 hour documentaries with very little problem, but now I cant even manage a one minute clip.
Not sure what to do. Here is a screen shot of my memory usage. Im getting massive swap memory and lots of inactive memory. It seems very strange. Especially after only 10 minutes running only final cut.FCP is only using 409 MBs of memory out of your 4 GBs. But whatever else you have open is using up virtually all the physical RAM you have. This is forcing the memory manager to page memory out to the disk-based VM file. That's a major reason for major slowdowns.
You have 4 GBs of RAM. How many applications are you running concurrently? If you look at Page outs: you will note the positive number in parentheses. That means your computer is hitting the hard drive a lot because the memory demands are too high. If possible cut down on how many concurrent applications you run or put more RAM into the computer, if that's possible.
About OS X Memory Management and Usage
Using Activity Monitor to read System Memory & determine how much RAM is used
Memory Management in Mac OS X
Performance Guidelines- Memory Management in Mac OS X
A detailed look at memory usage in OS X
Understanding top output in the Terminal
The amount of available RAM for applications is the sum of Free RAM and Inactive RAM. This will change as applications are opened and closed or change from active to inactive status. The Swap figure represents an estimate of the total amount of swap space required for VM if used, but does not necessarily indicate the actual size of the existing swap file. If you are really in need of more RAM that would be indicated by how frequently the system uses VM. If you open the Terminal and run the top command at the prompt you will find information reported on Pageins () and Pageouts (). Pageouts () is the important figure. If the value in the parentheses is 0 (zero) then OS X is not making instantaneous use of VM which means you have adequate physical RAM for the system with the applications you have loaded. If the figure in parentheses is running positive and your hard drive is constantly being used (thrashing) then you need more physical RAM.
Adding RAM only makes it possible to run more programs concurrently. It doesn't speed up the computer nor make games run faster. What it can do is prevent the system from having to use disk-based VM when it runs out of RAM because you are trying to run too many applications concurrently or using applications that are extremely RAM dependent. It will improve the performance of applications that run mostly in RAM or when loading programs. -
Neat Trick! Free memory run Repair Permissions...
Ok, this one baffles me, I'm wondering if its just my MBP setup or if this will work for anyone. I noticed that if I run Disk Utility and Repair Permissions after starting up I free up almost 300megs of memory. Yes 300 MEG! Even if there are no permission problems to fix...
When I start up I have around 1112 Meg free memory and another 300-400 of used inactive memory. If I run DU and repair permissions my free memory shoots up to 1442 MEG Free.
Could someone else give this a try and let me know if the same happens for you. If it does I'd sure like to know why.
I realize this isn't an earth shattering thing here but it is a little puzzling, at least to me...
Would love to hear others results with this...
Cheers,
PeterThe only app that appears to display all running processes (if you can get them to display properly) is "top." Open the Terminal and run top at the prompt. If you have the Developer Tools installed you could try using the included utility called BigTop. It's likely that the processes with lowest PIDs are the ones run at startup. I don't know the specific processes but I do know the startup sequence of events:
The first thing that runs at startup is the BootROM. It contains the POST or Power-On Self Test that checks basic hardware, sets the initial states for the CPU, RAM, and crucial hardware interfaces. It also verifies RAM. If the machine passes POST then you will hear the normal chime. If not you will hear one of five beep errors: one beep means no RAM installed; two beeps means the RAM is incompatible; three beeps means there are no good memory banks; four beeps means there is no good image in the BootROM; and five beeps means the processor is not operable.
Next is the initialization of Open Firmware which also checks for startup modifier keys (like OPTION or SHIFT.)
After initialization the Mac OS X system is located and control is transferred to BootX which initializes the kernel environment and drivers needed to boot the system. It also starts up the kernel initialization process. When loading the kernel environment BootX also attempts to load any previously cached set of device drivers. This is what's going on when you see the spinning gear on the startup screen.
Next the kernel initializes the I/O kit and starts launchd. Launchd manages all the system daemons for both the system and individual users.
If you open Activity Monitor then click on the PID column to sort the PIDs in ascending order, then from the drop down menu select All Processes, Hierarchically. You will see the order of processes handled by launchd which is the first process run after initialization. Process 0 is the kernel_task.
After launchd executes it runs the /etc/rc script that performs basic system initialization which in turn launches SystemStarter that runs the contents of the startupitems folder. Configuration data are stored in the /etc/hostconfig file.
Next comes the Login Window process which loads the user environment, then the Dock, Finder, and SystemUIServer followed by any Login Items. If this is an installation in progress it will also launch the Setup Assistant.
This completes the startup process. -
Massive memory leak when using Google (normal search, inactive, but logged into Google+)
Firefox has massive memory usage in recent times (runs up to over 3GB on Win7x64HP). I was not sure until now what caused it, since I have the browser open in the background most of the time. Commonly open pages are facebook, some news site (containing flash ads) and some other stuff for doing research. And Google - of course.
Normally I killed Firefox completely whenever I recognized the memory usage was way above normal, but this time I just kicked the google tab and (after 2mins of HDD action) the mem usage dropped by 2GB! I have no idea what causes this, but the rise of allocated mem is always very slowly and seems to build up over the day (2-3 times stand-by or hibernation included). I also just realized that the google tab keeps cpu usage of FireFox constantly by around 2%. An important side note: FF automatically logs on to Google+, maybe that's one of the reasons.
Has anyone the same issues? Is it rather a the fault of FF or Google? Will try surfing with Extensions deactivated the next days to see if the behavior continues...If you go to ''about:memory'' in the location bar you may find some of the info there of use, explanatory notes appear on mousover. It will help you figure out where the memory is going to.
* see also [[high memory usage]]
Some of the developers have been trying recently to improve how firefox uses memory, and have recently added ''about:memory'' as a diagnostic feature.
Using 3GB of memory for firefox is obviously abnormal, however some sites you use may be fairly intensive. It does often take quite a bit of effort to track down such problems, but sometimes new problems are identified and then fixed: either problems with firefox, or with specific sites or software. -
Repairing permssions & memory usage
Just wondering...
For some reason (curiosity, probably; I'm no power user), a while back I got MenuMeters. I've noticed something for some time that is probably nothing to be concerned about but has made me curious again.
After my iMac has running for a while, my used memory, which starts out less than 200MB, spikes up to more than 500MB. This after typically running only a browser (firefox) and mail (tbird), perhaps iTunes, which, other than an occasional use of Word, is about the only thing I use on a regular basis.
Now, getting to my question. When I repair permissions via Disk Utility, the used memory steadily decreases and my free memory increases--almost back to how they were when I first booted (just now, it went back to 173MB free, 596MB used, for example).
Again, I'm not saying this is a problem, I'm just curious why it does this.
Thanks...John
This may help you understand how OS X handles memory:
Mac OS X: Reading system memory usage in Activity Monitor.
As for it decreasing when you run Repair Permissions, that will be due to the pattern of disk accesses affecting the algorithms used for keeping stuff around. -
I'm on a MacPro, Snow Leopard, 10.6.8 and did software update to safari 5.1.4. Now I can't open Microsoft Word or Skype. I've done repair permissions, restarted. How can I fix ASAP? Wish I could dump this and go back to 5.1.2! Help!
Try this Safari5.1 from the installer package
http://www.filefactory.com/file/cc9005d/n/Safari.pkg.zip
The download worked better with Firefox not sure why. At the bottom of the page after the captcha>> slow down load is the Free link, it took about 4 minutes to download on my test. -
Message after repairing permissions on MB wit Leopard
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
This message came after I repaired permissions on MB with Leopard - any idea what it means and is it important or not - something to do with Remote Management which was selected at start up - can tis be deleted or removed and what is remote management anyway - I was not aware of it being in the Tiger OS version beofre I upgraded.
Thanks
RCIt's normal. Other people are getting it too. Just disregard it for now.
-Bmer
Mac Owners Support Group - Join us @ MacOSG.com
Mac611 Mobile Mac Support - about.Mac611.com
iTunes:MacOSG Podcast | YouTube.MacOSG.com
An Apple User Group -
Leopard on MacBook and MacBook Pro / running repair permissions
I upgraded both MacBook and MacBook Pro without major problems. I have been trying to repair permissions on the Mac Harddrive , and just get the spinning wheel. I have in the past run Onyx to perform routine maintenance tasks, but did not want to run any third party programs in relation to maintenance. Do I need to run it from the text tool disc? I never used to have to run it from disc.
Thanks.
Jon Pousette-DartI used Cocktail, Onyx, and YASU before Leopard, but had some problems with repairing disk permissions since upgrading to Leopard. Didn't know Cocktail had upgraded to Leopard. I'm impervious to snide remarks from self proclaimed experts.
We run a studio here north of NYC ( which is a standard ProTools HD Accel facility and won't touch Leopard for sometime) Leopard is on two laptops which seem to run good but slower since the Leopard upgrade. Might try the upgraded Cocktail.
As far as Beta Testors, That was the verbatim words out of level two Mac support. Their words not mine. Not one of the guys I talked to even planned on running Leopard on their own machines, as none of us in the pro community will either.
Having said that, it's on two of my laptops, just not the machines I run to do final mixes on.
Jon Pousette-Dart
www.pousette-dart.com -
Disk Utility: cannot Repair Permissions, even on Leopard installation disk
After reinstall of iLife '08 and Software Update completed, I ran Repair Disk Permissions. Got an immediate red note "error: The underlying task reported failure on exit (sic)." with a flag: "First Aid failed. Disk Utility stopped repairing permissions on 'Mac HD...' because the following error was encountered: The underlying task reported failure on exit."
I went to my Leopard Installation disk and ran "Repair Disk." No problem found. From the Installation disk, ran Repair Disk Permissions. got the same RED INK comments and flag, First Aid failed.
Restarts don't help. Also, so far I have not found an application which is NOT working despite this Disk Utility problem, happy to report ;-))
Additional background. I was reinstalling iLife to fix iPhoto after a clean reinstallation of Leopard and reincorporation of files and apps vis Time Machine. It had been several weeks and iPhoto appeared to be the only app which was not quite right.Disk Repair can trigger "underlying task" but I've never heard or seen a Permissions Repair do so.
You should never use the DVD to repair permissions. You should be using the same OS version. And of course you can always repair permissions from your boot drive; or from backup/clone or alternate "emergency" drive. Otherwise, the DVD and older version of DU will be wrong.
I know I read that on MacFixit, but I am not sure I bookmarked it.
Don't rely on Apple First Aid, even a clean bill of health doesn't mean there aren't problems which Disk Warrior can deal with. -
Yosemite and Mail massive memory leak and excessive CPU usage
I've just installed Yosemite and upgraded to 10.10.2 via the AppStore. Now I have a problem with Mail sucking up all the CPU (>106% !) and memory (>8Gb and rising while doing nothing). Everything runs fine when I quit Mail. Very disturbing behaviour!
I've tried several suggestions found elsewhere on the board here, such as turning off and even removing all Mail plug-ins including SpamSieve, but without positive results. I've tried un-selecting 'Store draft msgs on server', as well as the option for junk and sent msgs. but again without any difference. Going Offline within Mail also makes no difference to its memory hogging or CPU usage.
I notice this is an issue that's been around since last year (wish I'd known that before upgrading to Yosemite today) and I am just completely flabbergasted that it still exists. Would've thought Apple'd have fixed it in the first but certainly in the second incremental OSX Yosemite release.
Is there anything else I could try that's proven to be effective in stopping Mail's massive memory leak?Okay, I've run Disk Util and restarted. Seems to have made a little bit of a difference to the RAM gobbling in that it appears to be going at a slower rate, but it's still up at around the 45Gb after an hour. Here's the EtreCheck report in the hope that it helps.
EtreCheck version: 2.1.6 (109)
Report generated 28 January 2015 4:38:22 pm AEDT
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Support] links for help with non-Apple products.
Click the [Details] links for more information about that line.
Click the [Adware] links for help removing adware.
Hardware Information: ℹ️
MacBook Pro (Retina, 15-inch, Mid 2014) (Technical Specifications)
MacBook Pro - model: MacBookPro11,3
1 2.5 GHz Intel Core i7 CPU: 4-core
16 GB RAM Not upgradeable
BANK 0/DIMM0
8 GB DDR3 1600 MHz ok
BANK 1/DIMM0
8 GB DDR3 1600 MHz ok
Bluetooth: Good - Handoff/Airdrop2 supported
Wireless: en0: 802.11 a/b/g/n/ac
Battery Health: Normal - Cycle count 16
Video Information: ℹ️
Intel Iris Pro
Color LCD spdisplays_2880x1800Retina
NVIDIA GeForce GT 750M - VRAM: 2048 MB
System Software: ℹ️
OS X 10.10.2 (14C109) - Time since boot: 1:1:19
Disk Information: ℹ️
APPLE SSD SM0512F disk0 : (500.28 GB)
EFI (disk0s1) <not mounted> : 210 MB
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
Macintosh HD (disk1) / : 499.05 GB (413.24 GB free)
Core Storage: disk0s2 499.42 GB Online
USB Information: ℹ️
Apple Internal Memory Card Reader
Asmedia ASM107x
Asmedia ASM107x
Apple Inc. Apple Internal Keyboard / Trackpad
Apple Inc. BRCM20702 Hub
Apple Inc. Bluetooth USB Host Controller
Asmedia ASM107x
Asmedia ASM107x
Logitech Logitech USB Optical Mouse
Apple, Inc. Keyboard Hub
Apple, Inc Apple Keyboard
Thunderbolt Information: ℹ️
Apple Inc. thunderbolt_bus
Configuration files: ℹ️
/etc/hosts - Count: 2
Gatekeeper: ℹ️
Mac App Store and identified developers
Kernel Extensions: ℹ️
/Applications/DiskWarrior.app
[not loaded] com.alsoft.Preview (5 - SDK 10.5) [Support]
/Applications/ibVPN.app
[not loaded] net.tunnelblick.tap (1.0) [Support]
[not loaded] net.tunnelblick.tun (1.0) [Support]
/Library/Extensions
[loaded] at.obdev.nke.LittleSnitch (4231 - SDK 10.8) [Support]
[loaded] com.sophos.kext.sav (9.2.50 - SDK 10.8) [Support]
[loaded] com.sophos.nke.swi (9.2.50 - SDK 10.8) [Support]
[loaded] jp.plentycom.driver.SteerMouse (4.2.2 - SDK 10.6) [Support]
Problem System Launch Agents: ℹ️
[killed] com.apple.AirPlayUIAgent.plist
[killed] com.apple.CallHistoryPluginHelper.plist
[killed] com.apple.CallHistorySyncHelper.plist
[killed] com.apple.cloudd.plist
[killed] com.apple.icloud.fmfd.plist
[killed] com.apple.nsurlsessiond.plist
[killed] com.apple.pluginkit.pkd.plist
[killed] com.apple.security.cloudkeychainproxy.plist
[killed] com.apple.spindump_agent.plist
[killed] com.apple.telephonyutilities.callservicesd.plist
10 processes killed due to memory pressure
Problem System Launch Daemons: ℹ️
[killed] com.apple.awdd.plist
[killed] com.apple.ctkd.plist
[killed] com.apple.icloud.findmydeviced.plist
[killed] com.apple.ifdreader.plist
[killed] com.apple.nehelper.plist
[killed] com.apple.nsurlsessiond.plist
[killed] com.apple.softwareupdated.plist
[killed] com.apple.wdhelper.plist
8 processes killed due to memory pressure
Launch Agents: ℹ️
[running] at.obdev.LittleSnitchUIAgent.plist [Support]
[not loaded] com.adobe.AAM.Updater-1.0.plist [Support]
[running] com.adobe.AdobeCreativeCloud.plist [Support]
[running] com.sophos.uiserver.plist [Support]
Launch Daemons: ℹ️
[running] at.obdev.littlesnitchd.plist [Support]
[running] com.adobe.adobeupdatedaemon.plist [Support]
[loaded] com.adobe.fpsaud.plist [Support]
[loaded] com.microsoft.office.licensing.helper.plist [Support]
[running] com.sophos.common.servicemanager.plist [Support]
[running] com.synium.cleanappdaemon.plist [Support]
[running] com.syniumsoftware.CleanAppDaemon.plist [Support]
User Launch Agents: ℹ️
[loaded] com.adobe.ARM.[...].plist [Support]
[running] com.c-command.SpamSieve.LaunchAgent.plist [Support]
[loaded] com.google.keystone.agent.plist [Support]
[not loaded] com.linotype.FontFolderProtector.plist [Support]
[failed] com.wondershare.mobilegodaemon.plist [Support]
[not loaded] info.lokiware.attachmenttamer.cleanup.plist [Support]
[invalid?] info.lokiware.attachmenttamer.setupagent.plist [Support]
User Login Items: ℹ️
Letter Opener Updater Application (/Library/Mail/Bundles/Letter Opener.mailbundle/Contents/Resources/Software Update.app)
iTunesHelper Application (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)
Default Folder X Helper Application Hidden (/Users/[redacted]/Library/PreferencePanes/Default Folder X.prefPane/Contents/Resources/Default Folder X Helper.app)
FontExplorer X Pro Application Hidden (/Applications/FontExplorer X Pro.app)
Calendar Application Hidden (/Applications/Calendar.app)
SteerMouse Manager Application (/Applications/Utilities/SteerMouse.app/Contents/MacOS/SteerMouse Manager.app)
Mail Application Hidden (/Applications/Mail.app)
Android File Transfer Agent Application (/Users/[redacted]/Library/Application Support/Google/Android File Transfer/Android File Transfer Agent.app)
DiskWarriorStarter Application (/Applications/DiskWarrior.app/Contents/Helpers/DiskWarriorStarter.app)
finderpop-daemon Application (/Users/[redacted]/Library/PreferencePanes/FinderPop.prefPane/Contents/Resource s/finderpop-daemon.app)
XtraFinder Application Hidden (/Applications/XtraFinder.app)
Internet Plug-ins: ℹ️
AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 [Support]
FlashPlayer-10.6: Version: 16.0.0.296 - SDK 10.6 [Support]
QuickTime Plugin: Version: 7.7.3
AdobePDFViewerNPAPI: Version: 11.0.10 - SDK 10.6 [Support]
AdobePDFViewer: Version: 11.0.10 - SDK 10.6 [Support]
Flash Player: Version: 16.0.0.296 - SDK 10.6 [Support]
Default Browser: Version: 600 - SDK 10.10
SharePointBrowserPlugin: Version: 14.4.7 - SDK 10.6 [Support]
User internet Plug-ins: ℹ️
iGetter Plugin: Version: 2.9.3 [Support]
iGetterScriptablePlugin: Version: 2.9.3 [Support]
Safari Extensions: ℹ️
1Password [Installed]
iGetter Extension [Installed]
3rd Party Preference Panes: ℹ️
Default Folder X [Support]
FinderPop [Support]
FUSE for OS X (OSXFUSE) [Support]
SteerMouse [Support]
Time Machine: ℹ️
Time Machine not configured!
Top Processes by CPU: ℹ️
105% Mail
3% WindowServer
2% sysmond
2% Activity Monitor
0% fontd
Top Processes by Memory: ℹ️
4.10 GB Mail
103 MB Finder
86 MB SophosScanD
86 MB InterCheck
86 MB WindowServer
Virtual Memory Information: ℹ️
84 MB Free RAM
2.92 GB Active RAM
2.87 GB Inactive RAM
2.76 GB Wired RAM
2.57 GB Page-ins
23 MB Page-outs
Diagnostics Information: ℹ️
Jan 28, 2015, 03:37:41 PM Self test - passed
Jan 28, 2015, 02:49:01 PM /Users/[redacted]/Library/Logs/DiagnosticReports/Android File Transfer Agent_2015-01-28-144901_[redacted].crash
Jan 28, 2015, 09:31:04 AM /Library/Logs/DiagnosticReports/Mail_2015-01-28-093104_[redacted].cpu_resource. diag [Details]
Jan 28, 2015, 07:39:17 AM /Library/Logs/DiagnosticReports/AdobeCrashDaemon_2015-01-28-073917_[redacted].c rash
Jan 27, 2015, 07:54:29 PM /Library/Logs/DiagnosticReports/AdobeCrashDaemon_2015-01-27-195429_[redacted].c rash -
Leopard DU not repairing permissions
Hi there
I have a 1.8Ghz G5 (2.5Gb RAM) PowerMac here, running Leopard 10.5.8, which is used as a file server. The drives aren't RAIDed or anything. I am going to add a 2nd internal drive to it, and as a maintenance I decided to repair pemrissions before shutting it down.
However, when I ran Disk Utility, I found that I cound't repair permissions at all. I could select the drive, click the botton, and the progression bar would go to the 'striped barber pole' effect that comes up as it is preparing to do something, but then it just stays there. I can cancel it, but no repairs happen.
Any ideas how to get this to work or should I just use a 3rd party solution like Leopard Cache Cleaner? I'm not sure whether other software would just come up against the same issue.
Thanks**UPDATE**
Emergency over. It took about 30mins, but it did in the end actually work.
Sorry to waste you time, bandwidth, and server space. -
Repair Disk & Repair Permissions Using Leopard Install Disk NOT WORKING!!
I start up from my Leopard disk and click the Mac OS Partition in disk utility and two things go wrong...
Firstly, when I click either verify or repair permissions the progress bar stays as the moving angled lines forever (haven't tried leaving it for more than five minutes though).
Secondly, when I verify my disk it says everything appears to be okay, but when I try and repair the disk it says "The disk Macintosh HD cannot be unmounted" so I am unable to repair my disk. Are these fixable issues or is it a Leopard thing?UPDATE: I let Repair Permissions run for a good twenty minutes and it worked, just took a long time, this in turn fixed my Repair Disk problem, so I'm all set.
-
Massive memory hemorrhage; heap size to go from about 64mb, to 1.3gb usage
**[SOLVED]**
Note: I posted this on stackoverflow as well, but a solution was not found.
Here's the problem:
[1] http://i.stack.imgur.com/sqqtS.png
As you can see, the memory usage balloons out of control! I've had to add arguments to the JVM to increase the heapsize just to avoid out of memory errors while I figure out what's going on. Not good!
##Basic Application Summary (for context)
This application is (eventually) going to be used for basic on screen CV and template matching type things for automation purposes. I want to achieve as high of a frame rate as possible for watching the screen, and handle all of the processing via a series of separate consumer threads.
I quickly found out that the stock Robot class is really terrible speed wise, so I opened up the source, took out all of the duplicated effort and wasted overhead, and rebuilt it as my own class called FastRobot.
##The Class' Code:
public class FastRobot {
private Rectangle screenRect;
private GraphicsDevice screen;
private final Toolkit toolkit;
private final Robot elRoboto;
private final RobotPeer peer;
private final Point gdloc;
private final DirectColorModel screenCapCM;
private final int[] bandmasks;
public FastRobot() throws HeadlessException, AWTException {
this.screenRect = new Rectangle(Toolkit.getDefaultToolkit().getScreenSize());
this.screen = GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice();
toolkit = Toolkit.getDefaultToolkit();
elRoboto = new Robot();
peer = ((ComponentFactory)toolkit).createRobot(elRoboto, screen);
gdloc = screen.getDefaultConfiguration().getBounds().getLocation();
this.screenRect.translate(gdloc.x, gdloc.y);
screenCapCM = new DirectColorModel(24,
/* red mask */ 0x00FF0000,
/* green mask */ 0x0000FF00,
/* blue mask */ 0x000000FF);
bandmasks = new int[3];
bandmasks[0] = screenCapCM.getRedMask();
bandmasks[1] = screenCapCM.getGreenMask();
bandmasks[2] = screenCapCM.getBlueMask();
Toolkit.getDefaultToolkit().sync();
public void autoResetGraphicsEnv() {
this.screenRect = new Rectangle(Toolkit.getDefaultToolkit().getScreenSize());
this.screen = GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice();
public void manuallySetGraphicsEnv(Rectangle screenRect, GraphicsDevice screen) {
this.screenRect = screenRect;
this.screen = screen;
public BufferedImage createBufferedScreenCapture(int pixels[]) throws HeadlessException, AWTException {
// BufferedImage image;
DataBufferInt buffer;
WritableRaster raster;
pixels = peer.getRGBPixels(screenRect);
buffer = new DataBufferInt(pixels, pixels.length);
raster = Raster.createPackedRaster(buffer, screenRect.width, screenRect.height, screenRect.width, bandmasks, null);
return new BufferedImage(screenCapCM, raster, false, null);
public int[] createArrayScreenCapture() throws HeadlessException, AWTException {
return peer.getRGBPixels(screenRect);
public WritableRaster createRasterScreenCapture(int pixels[]) throws HeadlessException, AWTException {
// BufferedImage image;
DataBufferInt buffer;
WritableRaster raster;
pixels = peer.getRGBPixels(screenRect);
buffer = new DataBufferInt(pixels, pixels.length);
raster = Raster.createPackedRaster(buffer, screenRect.width, screenRect.height, screenRect.width, bandmasks, null);
// SunWritableRaster.makeTrackable(buffer);
return raster;
}In essence, all I've changed from the original is moving many of the allocations from function bodies, and set them as attributes of the class so they're not called every time. Doing this actually had a significant affect on frame rate. Even on my severely under powered laptop, it went from ~4 fps with the stock Robot class, to ~30fps with my FastRobot class.
##First Test:
When I started outofmemory errors in my main program, I set up this very simple test to keep an eye on the FastRobot. Note: this is the code which produced the heap profile above.
public class TestFBot {
public static void main(String[] args) {
try {
FastRobot fbot = new FastRobot();
double startTime = System.currentTimeMillis();
for (int i=0; i < 1000; i++)
fbot.createArrayScreenCapture();
System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
} catch (AWTException e) {
e.printStackTrace();
}##Examined:
It doesn't do this every time, which is really strange (and frustrating!). In fact, it rarely does it at all with the above code. However, the memory issue becomes easily reproducible if I have multiple for loops back to back.
#Test 2
public class TestFBot {
public static void main(String[] args) {
try {
FastRobot fbot = new FastRobot();
double startTime = System.currentTimeMillis();
for (int i=0; i < 1000; i++)
fbot.createArrayScreenCapture();
System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
startTime = System.currentTimeMillis();
for (int i=0; i < 500; i++)
fbot.createArrayScreenCapture();
System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
startTime = System.currentTimeMillis();
for (int i=0; i < 200; i++)
fbot.createArrayScreenCapture();
System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
startTime = System.currentTimeMillis();
for (int i=0; i < 1500; i++)
fbot.createArrayScreenCapture();
System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
} catch (AWTException e) {
e.printStackTrace();
}##Examined
The out of control heap is now reproducible I'd say about 80% of the time. I've looked all though the profiler, and the thing of most note (I think) is that the garbage collector seemingly stops right as the fourth and final loop begins.
The output form the above code gave the following times:
Time taken: 24.282 //Loop1
Time taken: 11.294 //Loop2
Time taken: 7.1 //Loop3
Time taken: 70.739 //Loop4
Now, if you sum the first three loops, it adds up to 42.676, which suspiciously corresponds to the exact time that the garbage collector stops, and the memory spikes.
[2] http://i.stack.imgur.com/fSTOs.png
Now, this is my first rodeo with profiling, not to mention the first time I've ever even thought about garbage collection -- it was always something that just kind of worked magically in the background -- so, I'm unsure what, if anything, I've found out.
##Additional Profile Information
[3] http://i.stack.imgur.com/ENocy.png
Augusto suggested looking at the memory profile. There are 1500+ `int[]` that are listed as "unreachable, but not yet collected." These are surely the `int[]` arrays that the `peer.getRGBPixels()` creates, but for some reason they're not being destroyed. This additional info, unfortunately, only adds to my confusion, as I'm not sure why the GC wouldn't be collecting them
##Profile using small heap argument -Xmx256m:
At irreputable and Hot Licks suggestion I set the max heap size to something significantly smaller. While this does prevent it from making the 1gb jump in memory usage, it still doesn't explain why the program is ballooning to its max heap size upon entering the 4th iteration.
[4] http://i.stack.imgur.com/bR3NP.png
As you can see, the exact issue still exists, it's just been made smaller. ;) The issue with this solution is that the program, for some reason, is still eating through all of the memory it can -- there is also a marked change in fps performance from the first the iterations, which consume very little memory, and the final iteration, which consumes as much memory as it can.
The question remains why is it ballooning at all?
##Results after hitting "Force Garbage Collection" button:
At jtahlborn's suggestion, I hit the Force Garbage Collection button. It worked beautifully. It goes from 1gb of memory usage, down to the basline of 60mb or so.
[5] http://i.stack.imgur.com/x4282.png
So, this seems to be the cure. The question now is, how do I pro grammatically force the GC to do this?
##Results after adding local Peer to function's scope:
At David Waters suggestion, I modified the `createArrayCapture()` function so that it holds a local `Peer` object.
Unfortunately no change in the memory usage pattern.
[6] http://i.stack.imgur.com/Ky5vb.png
Still gets huge on the 3rd or 4th iteration.
#Memory Pool Analysis:
###ScreenShots from the different memory pools
##All pools:
[7] http://i.stack.imgur.com/nXXeo.png
##Eden Pool:
[8] http://i.stack.imgur.com/R4ZHG.png
##Old Gen:
[9] http://i.stack.imgur.com/gmfe2.png
Just about all of the memory usage seems to fall in this pool.
Note: PS Survivor Space had (apparently) 0 usage
##I'm left with several questions:
(a) does the Garbage Profiler graph mean what I think it means? Or am I confusing correlation with causation? As I said, I'm in an unknown area with these issues.
(b) If it is the garbage collector... what do I do about it..? Why is it stopping altogether, and then running at a reduced rate for the remainder of the program?
(c) How do I fix this?
Does anyone have any idea what's going on here?
[1]: http://i.stack.imgur.com/sqqtS.png
[2]: http://i.stack.imgur.com/fSTOs.png
[3]: http://i.stack.imgur.com/ENocy.png
[4]: http://i.stack.imgur.com/bR3NP.png
[5]: http://i.stack.imgur.com/x4282.png
[6]: http://i.stack.imgur.com/Ky5vb.png
[7]: http://i.stack.imgur.com/nXXeo.png
[8]: http://i.stack.imgur.com/R4ZHG.png
[9]: http://i.stack.imgur.com/gmfe2.png
Edited by: 991051 on Feb 28, 2013 11:30 AM
Edited by: 991051 on Feb 28, 2013 11:35 AM
Edited by: 991051 on Feb 28, 2013 11:36 AM
Edited by: 991051 on Mar 1, 2013 9:44 AMSO came through.
Turns out this issue was directly related to the garbage collector. The default one, for whatever reason, would get behind on its collection at points, and thus the memory would balloon out of control, which then, once allocated, became the new normal for the GC to operate at.
Manually setting the GC to ConcurrentMarkSweep solved this issue completely. After numerous tests, I have been unable to reproduce the memory issue. The garbage collector does an excellent job of keeping on top of these minor collections. -
Error Repairing Permissions in Snow Leopard
I repaired permissions before & after the 10.6.2 update. Got this error each time:
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
I guarantee you I was not messing around in there.Yeah ok, take it easy.
I was just saying that it was bizarre that we both posted exactly the same question mere minutes apart. My post is there, the same guy who answered yours answered mine a few seconds later, he just cut and pasted apparently.
I don't have too much time on my hands and I know my computer is listed as a G4, I have three Macs. One of which runs SL and had the same error message as you.
Can you re-read my post in the non confrontational way it was intended please. You ought to chill out a bit. -
Leopard Disc Permissions Corrupted, Won't Repair
1. TechTool support recommend that I check disc permissions to solve a login issue. Found that aprox. 100 were corrupted and would not repair. Here is one example: Permissions differ on "System/Library/PrivateFrameworks/CoreAUC.framework/ Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- . All the aprox. 100 corrupted permissions have the same "should be -rw-r--r-- , they are lrw-r--r-- " issue.
2. I did archive and install OSX, the machine hung after accepting log in. I then installed 0SX and brought my data over from TM. I then verified permissions and they were good.
3. I next installed updates, checked permissions again. This revealed that an update or updates seem to be corrupting permissions. They again would not accept repair. What can I do to address this? The machine seems to be working fine now but am concerned that system may be at risk. Please help. TonyWe are all getting those messages from Repair Permissions that say "Permissions differ..." and end with: "-rw-r--r--, they are lrw-r--r--" or something similar, the last set of letters beginning with an "l" which means it's a symbolic link, but is probably only meaningful to programmers.
They are not errors or warnings and as Apple says in the Knowledge Base article Lyssa pointed to, they can be safely ignored.
Maybe you are looking for
-
HDMI to VGA output possible (or will I get HDCP errors)?
Hello. Does anyone know if it's possible to use an HDMI-to-VGA cable with the ATV (gen2)? I purchased an ATV for my parents and they can't use it as every time they go to play a movie rental or stream Netflix, they get an HDCP error saying "the conne
-
Newbie Web Programmer. Does this require Flash or less?
Hey Guys! This is my first post and I am hoping you are not a bunch of sharks that are after my bleeding appendages. I need some guidance with a current web design project that I am doing. The site itself is a fixed framing of about 800 x 600 pixels.
-
Hi, I know how I can correct an inconsistency in the Firefox 4.0 beta 8, the error is: "sorry your browser is not support program by web dympro. " In IE there is a compatibility option firexfox view settings but can correct this error.
-
Will this work on my mini? Samsung SyncMaster 915N, and if so , is there any settings to change in the prefs panel for it to view properly?
-
How can I see a complete list of wired and wireless clients on an Airport Extreme?
As per the title, I cannot find a way in Airport Utility to see the wired clients, only the wireless ones. It's driving me nuts! Is there any other way of doing this via the Mac if the utility doesnt have this function? Thanks in advance.