Launchd and UserEventAgent hogging CPU

I've just taken delivery of a new MBPr for work and wanted to set up a second user account to keep my personal stuff separate.
When I log into this account, within minutes the fans start whirring, even though no programmes are running. According to Activity Monitor, launchd and UserEventAgent are using 77% and 48% of the cpu respectively.
When I log out, the problem goes away. I've tried deleting and the account and starting again, but to no avail.
Can anyone help?

Look at Applications -> Utilities -> Console
Chances are a launch daemon is trying to start and keeps dying, so it is launch again, and again, and again, ....
The Console should show the logs where you should see a repeating log entry for the failing daemon or launch agent.

Similar Messages

  • Mail and safari hogging cpu - corrupt preferences?

    I am having a major problem when I run Mail or Safari under Mavericks on my iMac - they hog all the CPU making it hard to do other things unless I keep quitting the Mail Web Content or Safari Web Content processes using Activity Monitor. This also has shown up in other discussions on this board and no one seems to have a resolution to the problem. But the curious thing is that I only have the problem on my older iMac, but on my new MacBook Pro that also runs Mavericks, runs Mail with identical settings (and is accessing the same server) and runs Safari with the same bookmarks there is no problem. So the problem must be with something on my iMac that is causing Mail and Safari to keep running these Web Content processes and taking over the CPU.
    In the old days I would have assumed it was a corrupt Preferences file and deleted that, but no one has sugggested this. Is this possible? If so, what should be deleted?

    While everything had been working fine, this morning I installed the latest update to the operating system and I am back with the same problem (although I am only having Mail Web Content hogging the CPU and not Safari Web content this time).  I am posting below some information from the log as you suggested (sorry if it is too much but I don't know what you are looking for). Let me know if there is anything else you need. Thanks for the help LInc.
    12/17/13 12:23:22.645 PM WindowServer[114]: disable_update_timeout: UI updates were forcibly disabled by application "Safari" for over 1.00 seconds. Server has re-enabled them.
    12/17/13 12:23:22.983 PM Safari[226]: CGWindowContextCreate: failed to create window context delegate.
    12/17/13 12:23:22.983 PM Safari[226]: CGWindowContextCreate: failed to create window context delegate.
    12/17/13 12:23:22.983 PM Safari[226]: CGContextSaveGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.181 PM Safari[226]: CGContextResetCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.184 PM Safari[226]: CGContextResetClip: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.188 PM Safari[226]: CGContextTranslateCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.206 PM Safari[226]: CGContextScaleCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.209 PM Safari[226]: CGContextSaveGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.212 PM Safari[226]: clip: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.215 PM Safari[226]: CGContextRestoreGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.219 PM Safari[226]: CGContextTranslateCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.222 PM Safari[226]: CGContextTranslateCTM: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.225 PM Safari[226]: CGContextRestoreGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.228 PM Safari[226]: CGContextSynchronize: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
    12/17/13 12:23:23.618 PM WindowServer[114]: common_reenable_update: UI updates were finally reenabled by application "Safari" after 1.97 seconds (server forcibly re-enabled them after 1.00 seconds)
    12/17/13 12:23:34.580 PM sandboxd[268]: ([440]) com.apple.WebKit(440) deny file-read-data /Library/Preferences/com.apple.security-common.plist
    12/17/13 12:27:55.684 PM com.apple.launchd.peruser.502[172]: (com.apple.mdworker.shared.01000000-0000-0000-0000-000000000000[382]) Exited: Killed: 9
    12/17/13 12:29:57.739 PM xpcproxy[449]: assertion failed: 13B42: xpcproxy + 3438 [EE7817B0-1FA1-3603-B88A-BD5E595DA86F]: 0x2
    12/17/13 12:29:58.415 PM recentsd[396]: Failed to get Mail account information in a timely manner
    12/17/13 12:30:04.973 PM com.apple.launchd.peruser.502[172]: (com.apple.PackageKit.InstallStatus) Throttling respawn: Will start in 9 seconds
    12/17/13 12:30:11.256 PM com.apple.IconServicesAgent[279]: Icon filename entry missing from bundle info dictionary for bundle at URL: file:///System/Library/PrivateFrameworks/MailService.framework/Versions/A/XPCSe rvices/com.apple.MailServiceAgent.xpc/
    12/17/13 12:30:14.797 PM WindowServer[114]: CGXGetConnectionProperty: Invalid connection 76299
    12/17/13 12:30:39.935 PM loginwindow[43]: Could not find image named 'NSApplication'.
    12/17/13 12:30:39.936 PM loginwindow[43]: Could not find image named 'hgfhfg'.
    12/17/13 12:30:44.539 PM WindowServer[114]: CGXGetConnectionProperty: Invalid connection 70411
    12/17/13 12:30:45.099 PM com.apple.SecurityServer[14]: Killing auth hosts
    12/17/13 12:30:45.099 PM com.apple.SecurityServer[14]: Session 100021 destroyed
    12/17/13 12:30:45.103 PM com.apple.SecurityServer[14]: Session 100023 created
    12/17/13 12:30:45.825 PM Wallet[233]: Unknown class 'SUUpdater', using 'NSObject' instead. Encountered in Interface Builder file at path /Applications/Wallet.app/Contents/Resources/English.lproj/MainMenu.nib.
    12/17/13 12:30:45.826 PM Wallet[233]: Could not connect the action checkForUpdates: to target of class NSObject
    12/17/13 12:30:47.135 PM com.apple.AppSandboxSMLoginItemEnabler[463]: FAILURE: Job com.acrylic.WalletAgent is not loaded in launchd.
    12/17/13 12:30:48.270 PM sandboxd[268]: ([400]) com.apple.WebKit(400) deny file-read-data /Library/Preferences/com.apple.security-common.plist
    12/17/13 12:31:16.272 PM VDCAssistant[466]: AVF error: AVDLoadAllAccelerators machine not supported
    12/17/13 12:31:17.108 PM Adobe Illustrator[231]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.
    12/17/13 12:31:17.108 PM Adobe Illustrator[231]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
    12/17/13 12:31:17.132 PM Adobe Illustrator[231]: CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
    12/17/13 12:36:00.218 PM mdworker[448]: (Normal) Import: Spotlight giving up on importing file after 481.542 seconds, (0 seconds in Spotlight importer plugin, was sizing:0) - diagnostic:0 - find suspect file using: sudo mdutil -t 4554493
    12/17/13 12:36:00.220 PM com.apple.launchd.peruser.502[172]: (com.apple.mdworker.shared.01000000-0000-0000-0000-000000000000[448]) Exited with code: 75
    12/17/13 12:40:05.535 PM WindowServer[114]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fb189ddd3b0(2001)
    12/17/13 12:40:05.600 PM WindowServer[114]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x7fb189ddd3b0(2001)
    12/17/13 12:40:05.601 PM WindowServer[114]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x7fb189ddd3b0(2001)
    12/17/13 12:42:24.368 PM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: Deferring.
    12/17/13 12:42:24.370 PM WindowServer[114]: CGXDisplayDidWakeNotification [2043353335863]: posting kCGSDisplayDidWake
    12/17/13 12:43:10.608 PM xpcproxy[474]: assertion failed: 13B42: xpcproxy + 3438 [EE7817B0-1FA1-3603-B88A-BD5E595DA86F]: 0x2
    12/17/13 12:43:32.092 PM WindowServer[114]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
    12/17/13 12:43:32.572 PM WindowServer[114]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 1.48 seconds (server forcibly re-enabled them after 1.00 seconds)
    12/17/13 12:43:46.758 PM WindowServer[114]: CGXSetWindowListSystemAlpha: Invalid window 156 (index 0/1)
    12/17/13 12:43:46.758 PM WindowServer[114]: CGXSetWindowListSystemAlpha: Invalid window 157 (index 0/1)
    12/17/13 12:44:02.078 PM mdworker[471]: (Normal) Import: Spotlight giving up on importing file after 480.36 seconds, (0 seconds in Spotlight importer plugin, was sizing:0) - diagnostic:0 - find suspect file using: sudo mdutil -t 4554493
    12/17/13 12:44:02.081 PM com.apple.launchd.peruser.502[172]: (com.apple.mdworker.shared.01000000-0000-0000-0000-000000000000[471]) Exited with code: 75
    12/17/13 12:44:38.201 PM Console[491]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
    12/17/13 12:44:40.829 PM WindowServer[114]: disable_update_timeout: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    12/17/13 12:44:41.949 PM WindowServer[114]: common_reenable_update: UI updates were finally reenabled by application "Console" after 2.12 seconds (server forcibly re-enabled them after 1.00 seconds)
    12/17/13 12:44:47.000 PM kernel[0]: ALF: ifnet_get_address_list_family error 12
    12/17/13 12:47:44.287 PM mdworker32[510]: CGSConnectionByID: 0 is not a valid connection ID.
    12/17/13 12:47:44.287 PM mdworker32[510]: CGSGetSpaceManagementMode: No connection with id 0x       0

  • Configd and SystemUIServer hogging CPU

    Hello all:
    I have been setting up my new computer (so the system is virtually as shipped) and I have some strange situation going on. configd and SystemUIServer keep pulsing every minute or so and hog about 25% of the CPU each for bursts lasting up to a minute or so. My Airport connection works, but I have had some trouble to get the system to connect to my closed and password protected network by default. I often have to reenter the network name and password.
    I have tried erasing the network password from the system keychain and reentering it on the preferred network panel of System preferences. I have also trashed the SystemConfiguration folder and reset the network settings, but the problem persists.
    If I turn the Airport off, the problem naturally goes away. Also, it seems to go away if I connect to my neighbor's very weak signal and open network.
    Is it possible that there may be an issue with my network configuration (Airport Extreme settings)? However, my older PPC macs do not complain at all.
    I am really stumped. Any ideas?
    Thanks,
    Juan-Pablo
    iMac Core 2 Duo 24 in   Mac OS X (10.4.7)  
    iMac G4 17 in and iBook G3 14 in   Mac OS X (10.4)  
    iMac G4 17 in and iBook G3 14 in   Mac OS X (10.4)  

    Look at Applications -> Utilities -> Console
    Chances are a launch daemon is trying to start and keeps dying, so it is launch again, and again, and again, ....
    The Console should show the logs where you should see a repeating log entry for the failing daemon or launch agent.

  • Windowserver suddenly hogs cpu with Lightroom and Photoshop

    I recently upgraded these software packages to 64bit and upgraded NIK plugins for each to the 64bit versions. Since then I've had problems with PS freezing while making adjustments using a NIK plugin (doesn't appear to be plug-in specific). Looking at the Activity Monitor I see windowserver up to 90+ cpu usage. Sometimes if I just wait it will recover, sometimes I have to shut everything down.
    Anyone seeing this problem while using this software and if so have you found a remedy? This never happened while using the 32bit versions of all these packages.

    My understanding is that windowserver is an OS X application independent of software used. My question is whether others have seen windowserver start hogging CPU time while this specific software was being used and any Mac remedies that solve the issue. It's not an Adobe question.

  • Safari hogging CPU and won't run

    Sorry for posting here, but I couldn't find the Safar for windows section.
    I run WinXP (fully up to date), with 2Gb RAM, (with one 1Gb on my gfx card), 1.8Ghz processor
    Having updated to the latest Safari I'm finding that it hogs CPU so much so that when I select a page from the top sites screen my PC locks up and I have to use the application manager to kill Safari.
    The same thing happens when I try to go to a website just by typing into the address bar.
    Anyone having similar issues, or able to help me out as to how to fix it?
    Thanks

    Try turning off plug-ins, java, javascript
    Empty history, caches, etc or go to where XP would store the application temp files, in Windows Vista/7 that is AppData\Local and \Roaming
    Disable or turn off extensions, 3rd party can break with any Safari update
    make sure you have current Flash etc
    I'd stick to Firefox or something - use NoScript, HTTPS Everywhere, FlashBlock, etc.

  • Gpib write or read sometimes hogs cpu

    I have written a simple vi to communicate and
    control a Stanford Research SR640 programmable filter.  It does a
    series of gpib writes and reads to get and set various controls on the
    instrument, and it works very well.  The problem comes when I try to
    call it from a more complex vi that controls the entire experiment. 
    Once the sr640 vi is linked into the big vi, it takes 10-20 seconds for
    the sr640 vi to return and it hogs the cpu, making even the mouse
    unresponsive, Windows task manager stops updating, etc.  This happens
    even when running the simple sr640 vi directly from its front panel
    with no other vi's executing.  In "lightbulb" mode, I can see that
    occassionally, the gpib write or read icons (from traditional gpib
    pallette) take a long time to return, and the cpu goes to 100%.
    If
    I remove the complex calling vi from memory, the problem goes away, ie
    the sr640 vi runs fine.  If I load the big vi back into memory, I
    reproducibly get the bad behavior when running the sr640 vi. Note that the big vi does not need to be running to cause trouble, only be loaded in memory.   If I
    delete the sr640 vi from the big vi, i.e. it is no longer called from
    the big vi, the sr640 vi again runs fine.
    Any idea what might be happening and how to go about debugging this?
    Thanks,
    Bob Shelby

    Thanks for the reply. 
    Attached is the SR640 vi and a calling vi that works just fine.
    Bob 
    Attachments:
    srs_filter_setparms.vi ‏42 KB
    test_sr640.vi ‏17 KB

  • Mobiledeviceservice.exe hogs CPU

    mobiledeviceservice.exe hogs CPU. It takes 98 to 99 % of resources.  Trying to upgrade the operating system to 5.0 but its been hung up in the back up process for 4 hours.

    I have a single core laptop it won't work eats 99% of cpu, it's the mobile device service. I couldn't update my iPhone 4 to the latest iOS5.
    Also I can't access iTunes to get my contact list or music from iTunes with my new iPhone 4S because I have to update to iTunes 10.5 to do that or buy a quard core laptop.
    I do have two quard core PC's on in shop and one in bits, but my laptop was always my backup, maybe I need a new laptop but can't afford one atm.

  • MDNS responder hogging CPU when connected to network

    Hi all.
    It seems whenever I'm connected to my work's network (either via wired or wireless) my mDNSResponder service starts hogging CPU. It generally starts at 0 and works its way up to 70-80% total CPU usage. I can kill it but within a few seconds it starts back up again.
    Any idea what the problem is or how to fix it? This has never been a problem in the past, and as far as I'm aware there have been no changes to the network.
    Thanks!

    My first psychic guess would be a messed up .cache, but...
    mDNSResponder (also known as mdnsd on some systems) is a daemon invoked at boot time to implement Multicast DNS and DNS Service Discovery.
    mDNSResponder listens UDP port 5353 for Multicast DNS Query packets.
    When it receives a query for which it knows an answer, mDNSResponder issues the appropriate Multicast DNS Reply packet.
    mDNSResponder also performs Multicast DNS Queries on behalf of client processes, and maintains a cache of the replies.
    mDNSResponder has no user-specifiable command-line argument, and users should not run mDNSResponder manually.
    To examine mDNSResponder's internal state, for debugging and disagnostic purposes, send it a SIGINFO signal, and it will then dump a snapshot summary of its internal state to /var/log/system.log, e.g.
    sudo killall -INFO mDNSResponder
    Also, not sure if this applies to OSX or not...
    http://www.linuxmanpages.com/man8/mDNSResponder.8.php

  • Select launchd and clickedout of the process. help

    I am new to mac and I think I made a big mistake, I went to Activity Monitor and select launchd and clicked out of the process, now the screen is blank. please help, I do not know what to do.

    apparently, everything looks normal, there will be no collateral damage?

  • Coreaudiod and UserEventAgent both not responding

    I noticed in Activity Monitor showing all process on a clean boot I get both coreaudiod and UserEventAgent both not responding. I though this might be something to do with sound but the funny thing is everything seems ok. Audio and video and the general running of the computer seems to be fine unless i had not looked in activity monitor i probably would not of noticed.
    If i quit both processes they dont appear again in red not responding.
    But if i start an app or play a sound ot video they both pop back up again as not responding yet the system functions as normal seemingly and sound and audio works fine.
    Any Ideas. Sure seems a little strange.

    OK fixed it after a bunch of research I found 2 plugins that can ause problems in the
    go to :
    Library\Audio\Plug-Ins folder
    I had a folder called HAL which had a plugin for protools which i dont have anyways and i deleted it. Also there is a app called Hear which had a plugin i deleted as well. So basically if you are having similar issues check the various plug-ins in these folders and try removing them The Protools one is a known culprit as well as the Hear one.

  • OS X 10.5.3 (and beyond) Increases CPU Power Draw?

    Hi all
    I've got another ongoing thread (2006 Mac Pro Elevated CPU Temps) where I've been attempting to determine why my 2006 Mac Pro was running so much warmer than I recall at time of purchase...
    By sheer luck, I seem to have stumbled on the cause... when I first noticed it, I was running 10.5.7 with the CPUs idling around 130F or so... as noted in that thread, I tried all sorts of things such as cleaning the dust out, reapplying the thermal paste, etc... all of which had no impact... for an unrelated issue, I decided to re-install OS X 10.5 base version and I was shocked to discover my CPU temps back down in the mid-90s F or so...
    I happened to have taken some screenshots of Hardware Monitor and was able to compare them against the current readings... under OS X 10.5 -> 10.5.2, each CPU draws ~10W @ idle; under 10.5.3 and beyond, the CPU draw increases to ~30W @ idle. Naturally, this extreme increase results in the aforementioned temperature increase... I'm not sure as to the cause but my immediate suspicion is that some low-power CPU mode is disabled in the later revisions...
    I've spoken to Apple about this and they're looking into it but in the mean time, I was wondering if anyone has any input on this?
    -Justin

    Interesting since Apple stated that they observed similar results on their test machine...
    I'll have to try stripping the machine down to the original components and seeing if it has an impact... although, I think I've done this already when I was exploring why the CPU temps were so high...
    When you say
    The hatter wrote:
    Probably it is your system and something in the way it is configured... everything from power source coming in, any UPS or surge or line conditioner, to the PSU, and then to video and other components...
    if it's not the components and I don't have a UPS (all I have is a surge protector - could that have some impact?), what might it be?
    Thanks again!
    -Justin

  • Firefox keeps freezing and using 50% cpu and memory usage shoots up most of the time it's when there's an auto update of anything addon, plugin or ff!

    Firefox keeps freezing and using 50% cpu and memory usage shoots up real fast and carries on going till it uses up all there is left. Most of the time it's when there's an auto update of anything addon, plugin or ff but not just neccessarily then! I find out it's happened when there's been an update after i restart and an extra webpage comes up with the particular addon/plugin/ff update. I have to restart most of time because nothing sorts it out. I'm using windows xp with the latest update of ff 13.0.1 it's not this version because it's been happening for a while. And it never started when i added a particular addon or plugin or when i added a new app to my pc either. Any idea as to what this may be or how i'd sort it out?
    Cheers

    Maybe disable hardware acceleration? This article should help: https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram

  • Flash player 11 is very glitchy on ALL browsers and makes my CPU usage 100%,Streaming media headache

    flash player 11 is very glitchy on ALL browsers and makes my CPU usage 100%, making all youtube and pandora or any streaming media a headache, i have a low-end but good quality Emachine with Windows 7 Sv pk. 1, AMD Athalon Processor 2650e 1.6 GHz 2GB ram 32-bit, which isn't that bad, it used to play HD videos and everything without a skip or lag, it is virus clean, and clean of any large bulky programs, the only thing that went wrong was the fact that the adobe flash updates slowly but surely made it worse, AND it will not let me roll-back to an older version anymore like it used to, so WTF is up? no one seems to have an answer for this, and it seems like ADOBE is doing everything in it's power to not let me ask this question or get it solved, maybe it's because I AM TOO SMART FOR IT AND KNOW IT'S A FAILURE. so please, anyone who actually has a degree in this field is welcome, but no BS anymore, i want answers.
    [moved to Flash Player forum]
    Message was edited by: sinious

    The jump to FP11 was pretty significant with Stage3D. Now Flash Player has a lower level access to your computers GPU to offload playing video and 3d rendering to the GPU. However if your systems GPU isn't up to the task you really won't see that performance gain.
    Enter H264 video decoding. A large segment of the Flash usage market is simply viewing video. For sites without fallback in mind (or don't mind software rendering fallback), video may suffer. Using the GPU accelerated video classes may make it difficult for your system to view playback. Disabling hardware acceleration as recommended above would revert you back to software (CPU) decoding to check if your system itself is the issue (and not all the new GPU additions). You did that yet you're still having an issue.
    Just to clarify, as I have an eMachine (for accounting), your computer is very much in the "budget" margin. You have a 3 year old single core 1.6ghz AM2 CPU with 512kb of L2. That's the K8 series. This is a very underpowered, single thread loving CPU. Only the most optimized Flash sites and lower end videos (720p or below) should play, but I'm not even sure if they'll "play well". It depends on your GPU.
    Also you should know they have an official list of unsupported chipsets and drivers based on many factors. Here's a list for FP11 and AIR3:
    http://helpx.adobe.com/x-productkb/multi/stage3d-unsupported-chipsets-drivers-flash.html
    Check the bottom of the screen to see what Flash is reporting your rendering mode is. For example, mine states:
    Your gpu supports Stage3D in both Baseline and Constrained profile!
    Baseline RenderMode:
    DirectX9
    Constrained RenderMode:
    DirectX9 (Baseline Constrained)
    This probably won't get better in the future for you. Flash is not a low end multimedia runtime. It does require and utilize high end hardware in a much more reliable way.

  • Launchd and scheduled jobs

    From what I've read, you can't rely on launchd for scheduled jobs - in my case I want to back up at 3am in the morning - upon it being woken by another application.
    Now that cron is disabled - how can I achieve this scheduled tasks?
    I cannot believe that Apple have released into production a component that simply does not work ( that relies on the machine being on 100% without sleeping etc ).

    Hi Stewart:
    I can't speak to 10.4.3, but in 10.4.2, I just rebuilt my /etc/crontab file the way I wanted it, because cron still is a part of 10.4.2, and my Mac stays on 24x7.
    Looking at the "OEM" version of Tiger's crontab, it appears that what they did was basically make a crontab file full of comment lines, so I guess when cron parsed it, there was nothing there telling cron that it had to launch something.
    So, if you make a bonafide crontab file, I think (in 10.4.3) you'll be okay. If you don't recall the format for the crontab file, or don't have access to an old legacy one from 10.2 or so (I never had 10.3 so don't know whether they used cron or launchd), I can post mine here, if you'd like, that you could use as a model. I'll check back sometime later this week and see if you'd like me to post it here.
    Anyhow, after I made a new crontab file, I had asked on this forum how to disable the launchd daily/weekly/monthly stuff. Although it isn't important to do so, I figured, why run it more often than once daily/weekly/monthly, at what I understood would be random times of day, if the jobs would even be run at all, based on all the reports about undesired behavior caused by reboot, sleep, etc.?
    Some smart person on this forum told me that I could take the three com.apple.periodic-daily/weekly/monthly.plist files and save them off somewhere else other than in /System/Library/LaunchDaemons. So I just tarballed 'em (tar -cvvvzf com.apple.periodic-\*.plist.tgz com.apple.periodic-monthly.plist com.apple.periodic-weekly.plist com.apple.periodic-daily.plist) and left the tarball right there in /System/Library/LaunchDaemons, then deleted the originals. If I ever need 'em again I can just "tar -xvvvzf com.apple.periodic-\*.plist.tgz".
    So as near as I can tell, I don't even have to fuss about whether the daily/weekly/monthly jobs are being launched by launchd, and as near as I can tell, the daily/weekly/monthly jobs are being run daily, weekly, and monthly, as appropriate, and at the desired times of day, by cron and crontab.
    Quicksilver G4   Mac OS X (10.4.2)  
    Quicksilver G4    
    Quicksilver G4    

  • Launchd and ClamXav Update

    Hi everybody,
    I have a little problem with launchd and clamXav. The updater for clamXav is in "/usr/local/clamXav/bin/freshclam", and when i'm running freshclam with following command, everything works fine:
    /usr/local/clamXav/bin/freshclam --quiet --log="/usr/local/clamXav/share/clamav/freshclam.log"
    No i tryed to manage the update process with launchd, so i made a .plist file in "/Library/LaunchDaemons/" named "com.user.clamxav-update.plist" with following content:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Label</key>
    <string>com.user.clamxav-update</string>
    <key>ProgramArguments</key>
    <array>
    <string>/usr/local/clamXav/bin/freshclam</string>
    <string>--quiet</string>
    <string>--log="/usr/local/clamXav/share/clamav/freshclam.log"</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>StartInterval</key>
    <integer>120</integer>
    </dict>
    </plist>
    After that i loaded the plist with "laundctl load /Library/LaunchDaemons/com.user.clamxav-update.plist" successfully und when looking into the launchd list the file is loaded.
    After about 5 - 10 minutes the file isn't loaded anymore, and when looking into the update log of frehclam i could see that nothning happend
    Could someone tell me, why the file is successfully loaded, but not excecuted?
    Greetz from Germany
    iPod Photo 60GB 1. Gen    

    Hi Bruno,
       Cron may not be dead but Launchd has some advantages and it will certainly do what you want. Besides, you should probably learn to use it anyway. Your job probably unloaded because launchd thought that your "daemon" died prematurely. If you check the logs you'll probably find something on that. It would probably be in the system.log given that the script is run as root.
       The thing you need to do is to remove the RunAtLoad key. As far as I know, you can't "mix-and-match" launch criteria. Besides, the RunAtLoad key is used to launch daemons that launchd is supposed to keep running. If it "crashes" right after launch, launchd thinks it's faulty and unloads the job. If you use only the StartInterval criteria it will work; I just did it. (to make sure it was run as root)
       You can certainly afford to wait a couple of minutes before running. Speaking of that, did you really want to update every couple of minutes? Every couple of hours would seem sufficient.
    Gary
    ~~~~
       The problem ... is that we have run out of dinosaurs to form oil with. Scientists working for the Department of Energy have tried to form oil using other animals; they've piled thousands of tons of sand and Middle Eastern countries on top of cows, raccoons, haddock, laboratory rats, etc., but so far all they have managed to do is run up an enormous bulldozer-rental bill and anger a lot of Middle Eastern persons. None of the animals turned into oil, although most of the laboratory rats developed cancer.
             -- Dave Barry, "Postpetroleum Guzzler"

Maybe you are looking for