IChat Gobbling 100% CPU

OK, this is odd. I'll explain how this happened in order, so please bare with the minutia.
I was watching a video podcast, HD size, on my MacBook. The CPU fans kicked up, like they always do (no discrete video).
While watching the video, I noticed a slight choppiness in changing spaces and other slight slowness in the system which is unusual, the MB can handle it.
The video finishes, I close the window, but the fans don't slow. Even after a little bit like they usually do. I finally check the Activity Moniter and see that iChat is using 90-100% of my CPU. Odd.
I close iChat, Finder starts using all the CPU (time machine isn't running and I'm basically sitting idle while this is happening).
I relaunch Finder. No problems. I open iChat again, back to 100%.
I uninstall Chax, no difference.
I restart the machine. Start iChat, still eating up 100%.
Any clues? Can I use Time Machine to go back to before this was happening? Or does TM not work like that?
Can I reinstall iChat?

As there was a problem with the AIM servers recently I would expect there to be syncing problems with some people's Buddy lists.
I expect this is what was going on.
1:41 PM Sunday; March 9, 2008

Similar Messages

  • Ichat consumes over 100% CPU in video chat mode.

    Hi,
    I just updated my MBP (mid 2009) with new Snow Leopard. Ever since then, some of applications hangs, especially ichat, Mail, iphoto, safari.
    Is it normal that iChat consumes over 100% CPU in video chat mode? Does everyone have the same problem?

    Hello all. Ralph, I really appreciate all of your help on these iChat threads. I too am having the same issues with CPU overload on both of my Macbook Pro 2.16 GHz machines. I believe I may have traced the problem to older, non-Core 2 Duo chip computers such as mine. I have an iChat crazy family - lots of us spread across the country. The ones who have newer machines with a Core 2 Duo do not have this problem. They have super crisp, normal CPU usage (never exceeding 80%) chats. Sadly, this is not the case when I try with either of my Macbook Pro's running the older chips.
    To clarify, I have also taken all of the steps mentioned here and in other threads to try to address the problem. I have reinstalled Snow Leopard, adjusted the maximum bandwith to as low as 200 kbps, tested my download, upload speeds, etc. Nothing seems to work. Ichat it essentially useless. I wish I had an answer for this issue. I assume Apple will address this in the next OS update.

  • Itunes 7.01. 100% CPU usage workaround

    I've discovered that, like a lot of users 7.01 is gobbling up CPU time when its running causing everything to go slowly or even grinding to a halt not matter if it's downloading, synching etc.....
    However..... if you minimise itunes to the task bar the CPU time drops....in my case from 100% to around 6% max !!!!!
    I never had this with ver 6 which I recently reverted back to but thought I'd give it (7.01) a try after a clean re-install of XP (alas no) and I'll soon be re-reverting to ver 6 again
    Self built Athlon 64 3400+ Nvidia 6800T 2gb mem 250 gb SATA   Windows XP Pro   5th Gen 60gb Black

    This may sound like the oddest thing I've ever heard, but it actually is true that "minimized iTunes" behaves in a far better way than "maximized iTunes" - and I'll never be able to understand why.
    In my case, it was with synching iPod with iTunes: minimized iTunes takes about 4 minutes, maximized iTunes takes more than 1 hour!!
    Go figure!!!

  • Why does iTunes use 100% CPU all the time, hogging my Macbook Air?

    Decided to post this here instead of the iTunes forum, since it might be related to hardware too.
    New owner of a 2011 13" Macbook Air, core i5 based.
    My problem started about 1 week ago, after it had run out of power completely one day. At the first boot after that it was incredibly sluggish, totally unusable. After waiting for 5 minutes and still being unresponsive, I turned it off and then back on. Then it booted fine. HOWEVER, ever since that time I noticed the following behavior:
    - iTunes stays at 100% + CPU all the time, mostly between 100-120%. Even if it's not playing. Even when I deleted the entire library and left it empty.
    - iStats reports CPU idle between 50-65%. However, CPU temperature is still about 55 degrees C (which, I think, is far less than what it should have been with 50% idle cpu). I can confirm the low temperature by touching the chasis.
    - the cursor freezes and jumps every few seconds, making the mac kind of unusable with iTunes open.
    This has been going on for 2 weeks now. The problem goes away every now and then (iTunes sometimes goes back to regular CPU usage of 3-5%), but most of the time it's there.
    Help!
    P.S.
    Mac OX X 10.7.2
    iTunes 10.5.2

    Cee Pee You, is a OS modification. Apple recommends that you un-install these prior to a OS update because Apple makes changes to the OS all the time which breaks programs like these.
    I avoid Unsanity LLC products like the plague. Notice the company is a Limited Liability Corporation (LLC), which makes it difficult to sue the company in case of a defective or malicious product. So the risk using their products is all yours. Their APE framework modules have been used for malicious purposes because anyone can write a module that uses the APE framework.
    I also avoid installing anything that requires a administrative password unless I completely trust the source, like Apple mostly. That admin password is the key to the security of our machines, not to be given out lightly or carelessly.
    You'll have to contact Unsanity's [email protected] because what I'm reading online is it's very difficult to remove as it doesn't "exist".
    http://forums.macosxhints.com/archive/index.php/t-3616.html

  • Lightroom is very slow, utilizes 100% CPU, then freezes or closes program.  How do I fix it?

    I am having a problem with Lightroom 5 being very slow, utilizing 100% CPU, then freezing or closing the program.  How do I fix it?
    I just upgraded to LR5 from LR3 on Sunday as well as CS6 from CS5 (which I have not tried out yet).  I spent several hours talking with Vamil, from LR Support Staff yesterday.  He was extremely helpful and kind and tried everything he could think of while remote-handling my PC and talking with me on the phone.  He deleted preferences, cache, temp files, updated graphics with a new replacement file from AMD site, then re-downloaded and reinstalled LR5. 
    It is still very slow and then freezes and closes down with a message of utilizing 100% CPU.  Within several seconds of using the brush in Develop, I started having lots of problems.  I could not even move the picture around.  The side screens would not disappear like they should.  And I could not move to another picture.  The day before I spent several hours trying to work on just 1 picture.  After all the changes yesterday, I tried to move from picture number 1 to about 130 after having not touched it for 10 minutes, and a half hour later, it still said, "Processing" with no picture coming up, just a blank prieview pane.
    LR Support suggested I get a new CPU though he thought according to specs mine should be ok and other programs were running fine.
    My PC is only 2 years old.
    I talked to HP briefly about CPU updates for my HP PC.  He said I probably do not have a problem but suggested I run self-diagnostics and maybe buy a new CPU anyway. 
    I ran diagnostics listed through the HP Support Assistant connection on my PC.  All was ok. 
    I still researched if I could buy a compatible CPU upgrade.  I cannot even find any CPUs still selling that are listed for my PC.  Best Buy Store said they could not even order a compatible CPU.  They said my Bus speed may not be big enough, so they suggest I get a new PC.  What Bus speed do I need?
    I have the following PC Setup:
         AMD Phenom II X6 1045T Processor 2.70 GHz with 6 Cores
              with 2700 MHz Base, 3200 MHz Boost, and 4000 System Bus Speed, and 95 watts;
         HP Pavilion Elite, HPE-500y, 900 GB Free, new in 2011;
         Windows 7, 64 Bit;
         RAM 16 GB, DDR3;
         Graphics AMD Radeon HD 6450;
         Nikon, D200, with Raw Files;
         External Hard Drive for Original Photos, 600 GB Free;
         LR Catalog and Library are on Main Hard Drive;
         Monitor, Sony CPD-200ES, new in 2004.
    I am thinking of buying a new monitor tonight mostly so I can do better photo work while enlarging the pictures to do it.  I am concerned that while it will help my viewing, it will take more power away, and make my usage of LR5 even worse.  Will a new monitor affect my performance?  I am looking at HP Monitors with IPS.  Is this the best recommended choice for LR and Photoshop CS6?
    I think I would like to stay with a 6 core processor since I need to have several items open for other non-Photoshop functions.  When running LR5, I had everything else closed.  With LR3, I was able to have other things open.
    I do not really want to buy a new computer and know that those I have talked with at this point are only guessing after looking for what they thought should fix it.  4 People from Lightroom Support have all thought I should not be having problems with my setup. 
    I bought one of the best computers 2 years ago.  Is it really obsolete already so that I cannot use LR5?  Is everyone else buying a new PC every 2 years?  I used to go 5-7 years. 
    Even though I have figured out some of what my PC has, I really do not know technically what I am talking about so am at the mercy of other's help.  Are there any solutions that might work short of buying a new computer?
    I also have taken 40th anniversary photos for some people and am waiting to give them as a free gift since I am not a professional at all.  I am hoping to get through this problem soon so that I can provide some nice memories for them.
    I have not gotten any further than trying to adjust 1 picture.  I have no comments on uploading speed, since I did that while still in LR3.
    Thank you for your time and help.

    I'm running LR with no speed issues on an Intel 17-860 quad core with about the same performance as your AMD Phenom II X6 1045T Processor. My system is also an HP, which originally had a single 1TB 7200 HDD. I've since added a second 2TB Black Caviar HDD, which provided no significant difference in LR's performance.
    AMD processors do not implement hyper-threading and don't need it. I'd start debug by process of elimination:
    1) Disconnect all externally attached USB, FireWire, or other externally connected devices except keyboard, mouse, and your single 1280 x1024 display. This includes all externally attached memory card readers, phones, ipads, etc.
    2) Reboot and logon as Administrator.
    3) Remove your Internet connection and turn off all Antivirus and firewall programs.
    4) Open LR and under Catalog Settings set 'Standard Preview Size' to 1440 (slightly larger than your display width). Under the Metadata tab here make sure 'Automatically Write changes into XMP is NOT checked.
    4) Create a 'New Catalog,' Create a new folder and add about 10 raw image file copies to it for testing, and Import it into the new catalog. In the Import module make sure under File Handling 'Render Previews' has 1:1 selected. Wait until all Preview building has completed in the Library module.
    Try editing these image files inside the new catalog as you were previously.

  • Queue consumer stops with 100% cpu usage

    I'm trying to use Berkeley DB queue with transactions. When I tested what happens when transactions with DB_APPEND are aborted I found that while it works and DB_CONSUME correctly skips over rolled back records, unfortunately extents that have those records are never deleted, which causes database to always grow. Next I tried DB_CONSUME with database opened using DB_INORDER flag and it seems there's a serious regression in Berkeley DB that causes it to loop indefinitely with 100% cpu usage when it encounters a rolled back record. I tested various versions and found that this bug doesn't happen with 5.1.29, but it is reproducible with 5.2.42, so this regression might have been introduced in 5.2. I have also tested 5.3 and 6.0, and both have this behavior. There may be something wrong with the way queue records are rolled back, one indication of that would be that in 5.1.29 doesn't have neither of the two problems I found with DB_QUEUE: extents are deleted after being consumed, and there are no issues when consuming with DB_INORDER either.
    You can find Python code to reproduce this issue here:
    https://gist.github.com/snaury/027a3c546f5b0a62a440
    Sorry for using Python and not e.g. C++, but it's a lot shorter that way.

    We have looked at the issues and they are valid.   We will roll the fixes out for this in our next release of BDB.   The test case was very useful and really helped to speed the process up.    If you have any questions, please contact me directly at [email protected]  Thanks again for bringing this to our attention.
    thanks
    mike

  • HP LaserJet Pro MFP M127fn - DNS issue, hundreds of UDP connections affects my router 100% CPU usage

    Hi all,
    We've bought about ten pieces (HP LaserJet Pro MFP M127fn), tested only one the other 9 are waiting for their time to be sent in our branch offices. The MFP works fine, no complains till later that day I noticed that our Mikrotik Router was struguling with high CPU usage, it took me some time to find the issue and it was the new bought MFP. Don't know why but it creates hundreds of UDP connections and almost 100% CPU usage goes to DNS service. As soon as I shutdown the MFP and delete all the connections everything goes back to normal. I've disabled almost all services (HP web service, Ipv6, SNMP, AirPrint, SLP, LPD, WS-Discovery, Bonjour), leaving only Ipv4 but without luck the issue persists. Here are some print screens confirming my saying:
    http://i.imgur.com/UiOPSiu.jpg
    http://i.imgur.com/dlgObPb.jpg
    http://i.imgur.com/4RmQhot.jpg
    http://i.imgur.com/oBuo9UO.jpg
    http://i.imgur.com/Zf77V6b.jpg
    Don't know if it is the same case but it look like, found this post that ha no answer to the issue: http://h30434.www3.hp.com/t5/Printer-Networking-and-Wireless/New-HP-LaserJet-Pro-MFP-M127fw-network-...
    Why does this happen? And how to solve my issue? Thank you in advance.

    Hi @EugenX ,
    I have brought your issue to the attention of an appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post serial numbers and case details.
    If you are unfamiliar with how the Forum's private message capability works, this Post has instructions.
    Thank You.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Gemini02
    I work on behalf of HP

  • This new version of FireFox is making me nutz! It is SUCKING 100% CPU time almost constantly. I could just pull my hair out. I wpdated once a month or so ag

    I tried to add this in the topic already open but it kept sending me through the unending rabbit holes!
    My question is: How do I figure out what release I was on, get rid of this one and got back to a functional firefox that moves in realtime. I already did all the reset and etc.... I just want to go back to the speed I had. This halting , hanging up misery of a browzer is Sad. I have had firefox for years and always recommended it ..... BUT NOT ANY MORE. I agree with the other poster ... there should be a rollback feature. Peoples time has value and right now FireFox is sucking the value down a rabbit hole.
    See Below Comment Feedback submitted before I finally got here:
    This new version of FireFox is making me nutz! It is SUCKING 100% CPU time almost constantly. I could just pull my hair out. I wpdated once a month or so ago and it slowed down..... but the latest update before I did the reset really slowed me down. I came here to fix it a couple of dayz ago and did the reset firefox and now it IS RUNNING SO POORLY AND SLOW I AM ABOUT TO KILL IT OFF MY MACHINE!!! Yes that is me yelling - and it happened in SSSSSSSSSSSSS LLLLLLLLL OOOOOOOO WWWWWWWWWW Motion. I have run all the security scans and cleanups ---this needs a fix ASAP!!! PS: The hang ups and slowness is EVERYWHERE I go. I only get speed doing programs not connected to ON LINE.

    Hello,
    The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information.
    Note: ''This will cause you to lose any Extensions, Open websites, and some Preferences.''
    To Reset Firefox do the following:
    #Go to Firefox > Help > Troubleshooting Information.
    #Click the "Reset Firefox" button.
    #Firefox will close and reset. After Firefox is done, it will show a window with the information that is imported. Click Finish.
    #Firefox will open with all factory defaults applied.
    Further information can be found in the [[Reset Firefox – easily fix most problems]] article.
    Did this fix your problems? Please report back to us!
    Thank you.

  • Firefox 15.0.1 stops responding (100% cpu) when a link opens in a new window.

    Whenever I click a link that is designed to open in a new window Firefox goes straight to 100% cpu usage and I have to go through the Windows "end now" sequence to close the program. I've tried opening one of the links in a new window but I think it was done in java not html (not sure if all the links are java when this happens as that's the only one I've tested). Not sure what details someone might need but this is on my Mom's older laptop with Windows XP Media Center Edition Ver. 2002 Service Pack 2. Hmmm just saw the SP2 will try to update and see what that does though I don't think that's the issue.

    So what is happening or not happening now ? The problem computer is your Moms, but I assume your own computer works ok. Have you tried that on the same internet connection as your Mom uses & visiting the same sites?
    Also try Internet Explorer. If that is also very slow the problem may not lie with Firefox.
    I suggest you try the Firefox Reset feature on your Mom's computer,
    * BUT first of all
    **make a note of the software extensions that are in use, and bookmark their download and support sites.
    ** back up the Firefox profile [[Back up and restore information in Firefox profiles]]
    * follow the instructions in the following article, after reading the caution about what will be lost
    **[[Reset Firefox preferences to troubleshoot and fix problems]]

  • 100% CPU Usage Overhead running EM DBConsole 11g on OEL-5.2

    After upgrading to OEL-5.2 and relinking all Oracle binaries, my old Oracle 11g installation, installed several months before on OEL-5.1, has been working well, including Enterprise Manager Database Console working nicely as always with respectful performance. Unfortunatelly, it lasted just several days.
    Yesterday I decided to uninstall the 11g completely and perform new clean installation (software and database) with the same configuration options and settings as before, including EM dbconsole, all configured using dbca. After completing the installation (EM was started automatically by dbca), oracle continued to suck 80-85% CPU time. In further few minutes CPU utilization raised up to 99% due to only one (always the same PID) client process - "oracleorcl (LOCAL=NO)". For first ten minutes I didn't care too much since I always enable Automatic Management in dbca. But after two hours, I started to worry. The process was still running, consuming sustained 99% of CPU power. No other system activity, no database activity, no disks activity at all!
    I was really puzzled since I installed and reinstalled the 11g at least 20 times on OEL-5.0 and 5.1, experimenting with ASM, raw devices, loopback devices and various combinations of installation options, but never experienced such a behaviour. It took me 3 minutes to log in to EM dbconsole as it was almost unusable performing too slow. After three hours CPU temperature was nearly 60 degrees celsius. I decided to shutdown EM and after that everything became quiet. Oracle was running normally. Started EM again, the problem was back again. Tracing enabled, it filled a 350 MB trace file in just 20 minutes. Reinstalling the software and database once again didn't help. Whenever EM is up, the CPU usage overhead of 99% persists.
    Here is a cca 23 minutes session summary report taken from EM dbconsole's Performance page. The trace file is too big to list it here, but it shows the same.
            Host CPU:  100%
    Active Sessions:  100%The details for the Selected 5 Minute Interval (the last 5 min interval) are shown as follow:
        TOP SESSIONS:  SYSMAN, Program: OMS
            Activity:  100%  
         TOP MODULES:  OEM.CacheModeWaitPool, Service: orcl
            Activity:  100%          
          TOP CLIENT:  Unnamed
            Activity:  99.1%
         TOP ACTIONS:  Unnamed (OEM.CacheModeWaitPool) (orcl)
            Activity:  100%
         TOP OBJECTS: SYSMAN.MGMT_JOB_EXEC_SUMMARY (Table)
            Activity:  100%
          TOP PL/SQL:  SYSMAN.MGMT_JOB_ENGINE.INSERT_EXECUTION
       PL/SQL Source:  SYSMAN.MGMT_JOB_ENGINE
         Line Number:  7135
            Activity:  100%
             TOP SQL:  SELECT EXECUTION_ID, STATUS, STATUS_DETAIL FROM MGMT_JOB_EXEC_SUMMARY
    WHERE JOB_ID = :B3 AND TARGET_LIST_INDEX = :B2 AND EXPECTED_START_TIME = :B1;
            Activity:  100%
                                  STATISTICS SUMMARY
                                cca 23 minutes session
                            with no other system activity
                                            Per 
                           Total      Execution         Per Row
    Executions           105,103                 1       10,510.30
    Elapsed Time (sec)  1,358.95              0.01        135.90
    CPU Time (sec)      1,070.42             0.01        107.04
    Buffer Gets       85,585,518 814.30 8,558,551.80
    Disk Reads                 2            <0.01          0.20
    Direct Writes              0              0.00          0.00
    Rows                      10            <0.01             1
    Fetches              105,103             1.00     10,510.30
                       ----------------------------------------Wow!!! Note: no disk, no database activity !
    Has anyone experienced this or similar behaviour after clean 11g installation on OEL-5.2? If not, anyone has a clue what the hell is going on?
    Thanks in advance.

    Hi Tommy,
    I didn't want to experiment further with already working OEL-5.2, oracle and dbconsole on this machine, specially not after googling the problem and finding out that I am not alone in this world. There are another two threads on OTN forums (Database General) showing the same problem even on 2GB machines:
    DBConsole easting a CPU
    11g stuck. 50-100% CPU after fresh install
    So, I took another, a smaller free machine I've got at home (1GB RAM, 2.2MHz Pentium4, three 80GB disks), on which I used to experiment with new releases of software (this is the machine on which I installed 11g for the first time when it was released on OEL-5.0, and I can recall that everything was OK with EM). This is what I did:
    1. I installed OEL-5.0 on the machine, adjusted linux and kernel parameters, and performed full 11g installation. Database and EM dbconsole worked nice with acceptable performance. Without activity in the database, %CPU = zero !!! The whole system was perfectly quiet.
    2. Since everything was OK, I shutdown EM and oracle, and performed the full upgrade to OEL-5.2. When the upgrade finished, restarted the system, relinked all oracle binaries, and started oracle and EM dbconsole. Both worked perfectly again, just as before the upgrade. I repeated restarting the database and dbconsole several times, always with the same result - it really rocks. Without database activity, %CPU = zero%.
    3. Using dbca, I dropped the database and created the new one with the same configuration options. Wow! I'm again in trouble. A half an hour after the creation of the database, %CPU raised up to 99%. That's it.
    The crucial question here is: what is that in OEL-5.2, not existing in the 5.0, that causes dbca/em scripts to be embarrassed at the time of EM agent configuration?
    Here are the outputs you required picked 30 minutes after starting the database and EM dbconsole (sustained 99% CPU utilization). Note that this is just a 1GB machine.
    Kernel command line: ro root=LABEL=/ elevator=deadline rhgb quiet
    [root@localhost ~]# cat /proc/meminfo
    MemTotal:      1034576 kB
    MemFree:         27356 kB
    Buffers:          8388 kB
    Cached:         609660 kB
    SwapCached:      18628 kB
    Active:         675376 kB
    Inactive:       287072 kB
    HighTotal:      130304 kB
    HighFree:          260 kB
    LowTotal:       904272 kB
    LowFree:         27096 kB
    SwapTotal:     3148700 kB
    SwapFree:      2940636 kB
    Dirty:              72 kB
    Writeback:           0 kB
    AnonPages:      328700 kB
    Mapped:         271316 kB
    Slab:            21136 kB
    PageTables:      14196 kB
    NFS_Unstable:        0 kB
    Bounce:              0 kB
    CommitLimit:   3665988 kB
    Committed_AS:  1187464 kB
    VmallocTotal:   114680 kB
    VmallocUsed:      5860 kB
    VmallocChunk:   108476 kB
    HugePages_Total:     0
    HugePages_Free:      0
    HugePages_Rsvd:      0
    Hugepagesize:     4096 kB
    [root@localhost ~]# cat /proc/slabinfo
    slabinfo - version: 2.1
    # name            <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <limit> <batchcount> <sharedfactor> : slabdata <active_slabs> <num_slabs> <sharedavail>
    rpc_buffers            8      8   2048    2    1 : tunables   24   12    8 : slabdata      4      4      0
    rpc_tasks              8     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    rpc_inode_cache        6      7    512    7    1 : tunables   54   27    8 : slabdata      1      1      0
    ip_conntrack_expect    0      0     96   40    1 : tunables  120   60    8 : slabdata      0      0      0
    ip_conntrack          68     68    228   17    1 : tunables  120   60    8 : slabdata      4      4      0
    ip_fib_alias           7    113     32  113    1 : tunables  120   60    8 : slabdata      1      1      0
    ip_fib_hash            7    113     32  113    1 : tunables  120   60    8 : slabdata      1      1      0
    fib6_nodes            22    113     32  113    1 : tunables  120   60    8 : slabdata      1      1      0
    ip6_dst_cache         13     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    ndisc_cache            1     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    RAWv6                  4      5    768    5    1 : tunables   54   27    8 : slabdata      1      1      0
    UDPv6                  9     12    640    6    1 : tunables   54   27    8 : slabdata      2      2      0
    tw_sock_TCPv6          0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    request_sock_TCPv6     0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    TCPv6                  1      3   1280    3    1 : tunables   24   12    8 : slabdata      1      1      0
    jbd_1k                 0      0   1024    4    1 : tunables   54   27    8 : slabdata      0      0      0
    dm_mpath               0      0     28  127    1 : tunables  120   60    8 : slabdata      0      0      0
    dm_uevent              0      0   2460    3    2 : tunables   24   12    8 : slabdata      0      0      0
    dm_tio                 0      0     16  203    1 : tunables  120   60    8 : slabdata      0      0      0
    dm_io                  0      0     20  169    1 : tunables  120   60    8 : slabdata      0      0      0
    jbd_4k                 1      1   4096    1    1 : tunables   24   12    8 : slabdata      1      1      0
    scsi_cmd_cache        10     10    384   10    1 : tunables   54   27    8 : slabdata      1      1      0
    sgpool-128            36     36   2048    2    1 : tunables   24   12    8 : slabdata     18     18      0
    sgpool-64             33     36   1024    4    1 : tunables   54   27    8 : slabdata      9      9      0
    sgpool-32             34     40    512    8    1 : tunables   54   27    8 : slabdata      5      5      0
    sgpool-16             35     45    256   15    1 : tunables  120   60    8 : slabdata      3      3      0
    sgpool-8              60     60    128   30    1 : tunables  120   60    8 : slabdata      2      2      0
    scsi_io_context        0      0    104   37    1 : tunables  120   60    8 : slabdata      0      0      0
    ext3_inode_cache    4376   8216    492    8    1 : tunables   54   27    8 : slabdata   1027   1027      0
    ext3_xattr           165    234     48   78    1 : tunables  120   60    8 : slabdata      3      3      0
    journal_handle         8    169     20  169    1 : tunables  120   60    8 : slabdata      1      1      0
    journal_head         684   1008     52   72    1 : tunables  120   60    8 : slabdata     14     14      0
    revoke_table          18    254     12  254    1 : tunables  120   60    8 : slabdata      1      1      0
    revoke_record          0      0     16  203    1 : tunables  120   60    8 : slabdata      0      0      0
    uhci_urb_priv          0      0     28  127    1 : tunables  120   60    8 : slabdata      0      0      0
    UNIX                  56    112    512    7    1 : tunables   54   27    8 : slabdata     16     16      0
    flow_cache             0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    cfq_ioc_pool           0      0     92   42    1 : tunables  120   60    8 : slabdata      0      0      0
    cfq_pool               0      0     96   40    1 : tunables  120   60    8 : slabdata      0      0      0
    crq_pool               0      0     44   84    1 : tunables  120   60    8 : slabdata      0      0      0
    deadline_drq         140    252     44   84    1 : tunables  120   60    8 : slabdata      3      3      0
    as_arq                 0      0     56   67    1 : tunables  120   60    8 : slabdata      0      0      0
    mqueue_inode_cache     1      6    640    6    1 : tunables   54   27    8 : slabdata      1      1      0
    isofs_inode_cache      0      0    368   10    1 : tunables   54   27    8 : slabdata      0      0      0
    hugetlbfs_inode_cache  1     11    340   11    1 : tunables   54   27    8 : slabdata      1      1      0
    ext2_inode_cache       0      0    476    8    1 : tunables   54   27    8 : slabdata      0      0      0
    ext2_xattr             0      0     48   78    1 : tunables  120   60    8 : slabdata      0      0      0
    dnotify_cache          2    169     20  169    1 : tunables  120   60    8 : slabdata      1      1      0
    dquot                  0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    eventpoll_pwq          1    101     36  101    1 : tunables  120   60    8 : slabdata      1      1      0
    eventpoll_epi          1     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    inotify_event_cache    1    127     28  127    1 : tunables  120   60    8 : slabdata      1      1      0
    inotify_watch_cache   23     92     40   92    1 : tunables  120   60    8 : slabdata      1      1      0
    kioctx               135    135    256   15    1 : tunables  120   60    8 : slabdata      9      9      0
    kiocb                  0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    fasync_cache           0      0     16  203    1 : tunables  120   60    8 : slabdata      0      0      0
    shmem_inode_cache    553    585    436    9    1 : tunables   54   27    8 : slabdata     65     65      0
    posix_timers_cache     0      0     88   44    1 : tunables  120   60    8 : slabdata      0      0      0
    uid_cache              5     59     64   59    1 : tunables  120   60    8 : slabdata      1      1      0
    ip_mrt_cache           0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    tcp_bind_bucket       32    203     16  203    1 : tunables  120   60    8 : slabdata      1      1      0
    inet_peer_cache        1     59     64   59    1 : tunables  120   60    8 : slabdata      1      1      0
    secpath_cache          0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    xfrm_dst_cache         0      0    384   10    1 : tunables   54   27    8 : slabdata      0      0      0
    ip_dst_cache           6     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    arp_cache              2     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    RAW                    2      7    512    7    1 : tunables   54   27    8 : slabdata      1      1      0
    UDP                    3      7    512    7    1 : tunables   54   27    8 : slabdata      1      1      0
    tw_sock_TCP            3     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    request_sock_TCP       4     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    TCP                   43     49   1152    7    2 : tunables   24   12    8 : slabdata      7      7      0
    blkdev_ioc             3    127     28  127    1 : tunables  120   60    8 : slabdata      1      1      0
    blkdev_queue          23     24    956    4    1 : tunables   54   27    8 : slabdata      6      6      0
    blkdev_requests      137    161    172   23    1 : tunables  120   60    8 : slabdata      7      7      0
    biovec-256             7      8   3072    2    2 : tunables   24   12    8 : slabdata      4      4      0
    biovec-128             7     10   1536    5    2 : tunables   24   12    8 : slabdata      2      2      0
    biovec-64              7     10    768    5    1 : tunables   54   27    8 : slabdata      2      2      0
    biovec-16              7     15    256   15    1 : tunables  120   60    8 : slabdata      1      1      0
    biovec-4               8     59     64   59    1 : tunables  120   60    8 : slabdata      1      1      0
    biovec-1             406    406     16  203    1 : tunables  120   60    8 : slabdata      2      2    300
    bio                  564    660    128   30    1 : tunables  120   60    8 : slabdata     21     22    204
    utrace_engine_cache    0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    utrace_cache           0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    sock_inode_cache     149    230    384   10    1 : tunables   54   27    8 : slabdata     23     23      0
    skbuff_fclone_cache   20     20    384   10    1 : tunables   54   27    8 : slabdata      2      2      0
    skbuff_head_cache     86    210    256   15    1 : tunables  120   60    8 : slabdata     14     14      0
    file_lock_cache       22     40     96   40    1 : tunables  120   60    8 : slabdata      1      1      0
    Acpi-Operand        1147   1196     40   92    1 : tunables  120   60    8 : slabdata     13     13      0
    Acpi-ParseExt          0      0     44   84    1 : tunables  120   60    8 : slabdata      0      0      0
    Acpi-Parse             0      0     28  127    1 : tunables  120   60    8 : slabdata      0      0      0
    Acpi-State             0      0     44   84    1 : tunables  120   60    8 : slabdata      0      0      0
    Acpi-Namespace       615    676     20  169    1 : tunables  120   60    8 : slabdata      4      4      0
    delayacct_cache      233    312     48   78    1 : tunables  120   60    8 : slabdata      4      4      0
    taskstats_cache       12     53     72   53    1 : tunables  120   60    8 : slabdata      1      1      0
    proc_inode_cache     622    693    356   11    1 : tunables   54   27    8 : slabdata     63     63      0
    sigqueue               8     27    144   27    1 : tunables  120   60    8 : slabdata      1      1      0
    radix_tree_node     6220   8134    276   14    1 : tunables   54   27    8 : slabdata    581    581      0
    bdev_cache            37     42    512    7    1 : tunables   54   27    8 : slabdata      6      6      0
    sysfs_dir_cache     4980   4992     48   78    1 : tunables  120   60    8 : slabdata     64     64      0
    mnt_cache             36     60    128   30    1 : tunables  120   60    8 : slabdata      2      2      0
    inode_cache         1113   1254    340   11    1 : tunables   54   27    8 : slabdata    114    114     81
    dentry_cache       11442  18560    136   29    1 : tunables  120   60    8 : slabdata    640    640    180
    filp                7607  10000    192   20    1 : tunables  120   60    8 : slabdata    500    500    120
    names_cache           19     19   4096    1    1 : tunables   24   12    8 : slabdata     19     19      0
    avc_node              14     72     52   72    1 : tunables  120   60    8 : slabdata      1      1      0
    selinux_inode_security 814   1170     48   78    1 : tunables  120   60    8 : slabdata     15     15      0
    key_jar               14     30    128   30    1 : tunables  120   60    8 : slabdata      1      1      0
    idr_layer_cache      170    203    136   29    1 : tunables  120   60    8 : slabdata      7      7      0
    buffer_head        38892  39024     52   72    1 : tunables  120   60    8 : slabdata    542    542      0
    mm_struct            108    135    448    9    1 : tunables   54   27    8 : slabdata     15     15      0
    vm_area_struct     11169  14904     84   46    1 : tunables  120   60    8 : slabdata    324    324    144
    fs_cache              82    177     64   59    1 : tunables  120   60    8 : slabdata      3      3      0
    files_cache          108    140    384   10    1 : tunables   54   27    8 : slabdata     14     14      0
    signal_cache         142    171    448    9    1 : tunables   54   27    8 : slabdata     19     19      0
    sighand_cache        127    135   1344    3    1 : tunables   24   12    8 : slabdata     45     45      0
    task_struct          184    246   1360    3    1 : tunables   24   12    8 : slabdata     82     82      0
    anon_vma            3313   5842     12  254    1 : tunables  120   60    8 : slabdata     23     23      0
    pgd                   84     84   4096    1    1 : tunables   24   12    8 : slabdata     84     84      0
    pid                  237    303     36  101    1 : tunables  120   60    8 : slabdata      3      3      0
    size-131072(DMA)       0      0 131072    1   32 : tunables    8    4    0 : slabdata      0      0      0
    size-131072            0      0 131072    1   32 : tunables    8    4    0 : slabdata      0      0      0
    size-65536(DMA)        0      0  65536    1   16 : tunables    8    4    0 : slabdata      0      0      0
    size-65536             2      2  65536    1   16 : tunables    8    4    0 : slabdata      2      2      0
    size-32768(DMA)        0      0  32768    1    8 : tunables    8    4    0 : slabdata      0      0      0
    size-32768             9      9  32768    1    8 : tunables    8    4    0 : slabdata      9      9      0
    size-16384(DMA)        0      0  16384    1    4 : tunables    8    4    0 : slabdata      0      0      0
    size-16384             6      6  16384    1    4 : tunables    8    4    0 : slabdata      6      6      0
    size-8192(DMA)         0      0   8192    1    2 : tunables    8    4    0 : slabdata      0      0      0
    size-8192              5      5   8192    1    2 : tunables    8    4    0 : slabdata      5      5      0
    size-4096(DMA)         0      0   4096    1    1 : tunables   24   12    8 : slabdata      0      0      0
    size-4096            205    205   4096    1    1 : tunables   24   12    8 : slabdata    205    205      0
    size-2048(DMA)         0      0   2048    2    1 : tunables   24   12    8 : slabdata      0      0      0
    size-2048            260    270   2048    2    1 : tunables   24   12    8 : slabdata    135    135      0
    size-1024(DMA)         0      0   1024    4    1 : tunables   54   27    8 : slabdata      0      0      0
    size-1024            204    204   1024    4    1 : tunables   54   27    8 : slabdata     51     51      0
    size-512(DMA)          0      0    512    8    1 : tunables   54   27    8 : slabdata      0      0      0
    size-512             367    464    512    8    1 : tunables   54   27    8 : slabdata     58     58      0
    size-256(DMA)          0      0    256   15    1 : tunables  120   60    8 : slabdata      0      0      0
    size-256             487    495    256   15    1 : tunables  120   60    8 : slabdata     33     33      0
    size-128(DMA)          0      0    128   30    1 : tunables  120   60    8 : slabdata      0      0      0
    size-128            2242   2490    128   30    1 : tunables  120   60    8 : slabdata     83     83      0
    size-64(DMA)           0      0     64   59    1 : tunables  120   60    8 : slabdata      0      0      0
    size-32(DMA)           0      0     32  113    1 : tunables  120   60    8 : slabdata      0      0      0
    size-64             1409   2950     64   59    1 : tunables  120   60    8 : slabdata     50     50      0
    size-32             3596   3842     32  113    1 : tunables  120   60    8 : slabdata     34     34      0
    kmem_cache           145    150    256   15    1 : tunables  120   60    8 : slabdata     10     10      0
    [root@localhost ~]# slabtop -d 5
    Active / Total Objects (% used)    : 97257 / 113249 (85.9%)
    Active / Total Slabs (% used)      : 4488 / 4488 (100.0%)
    Active / Total Caches (% used)     : 101 / 146 (69.2%)
    Active / Total Size (% used)       : 15076.34K / 17587.55K (85.7%)
    Minimum / Average / Maximum Object : 0.01K / 0.16K / 128.00K
      OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME
    25776  25764  99%    0.05K    358       72      1432K buffer_head
    16146  15351  95%    0.08K    351       46      1404K vm_area_struct
    15138   7779  51%    0.13K    522       29      2088K dentry_cache
      9720   9106  93%    0.19K    486       20      1944K filp
      7714   7032  91%    0.27K    551       14      2204K radix_tree_node
      5070   5018  98%    0.05K     65       78       260K sysfs_dir_cache
      4826   4766  98%    0.01K     19      254        76K anon_vma
      4824   3406  70%    0.48K    603        8      2412K ext3_inode_cache
      3842   3691  96%    0.03K     34      113       136K size-32
      2190   2174  99%    0.12K     73       30       292K size-128
      1711   1364  79%    0.06K     29       59       116K size-64
      1210   1053  87%    0.33K    110       11       440K inode_cache
      1196   1147  95%    0.04K     13       92        52K Acpi-Operand
      1170    814  69%    0.05K     15       78        60K selinux_inode_security
       936    414  44%    0.05K     13       72        52K journal_head
       747    738  98%    0.43K     83        9       332K shmem_inode_cache
       693    617  89%    0.35K     63       11       252K proc_inode_cache
       676    615  90%    0.02K      4      169        16K Acpi-Namespace
       609    136  22%    0.02K      3      203        12K biovec-1
       495    493  99%    0.25K     33       15       132K size-256
       480    384  80%    0.12K     16       30        64K bio
       440    399  90%    0.50K     55        8       220K size-512
       312    206  66%    0.05K      4       78        16K delayacct_cache
       303    209  68%    0.04K      3      101        12K pid
       290    290 100%    0.38K     29       10       116K sock_inode_cache
    [root@localhost ~]# cat /etc/sysctl.conf
    # Kernel sysctl configuration file for Red Hat Linux
    # Controls IP packet forwarding
    net.ipv4.ip_forward=0
    # Controls source route verification
    net.ipv4.conf.default.rp_filter=1
    # Do not accept source routing
    net.ipv4.conf.default.accept_source_route=0
    # Oracle
    net.ipv4.ip_local_port_range=1024 65000
    net.core.rmem_default=4194304
    net.core.rmem_max=4194304
    net.core.wmem_default=262144
    net.core.wmem_max=262144
    net.ipv4.tcp_rmem=4096 65536 4194304
    net.ipv4.tcp_wmem=4096 65536 4194304
    # Keepalive Oracle
    net.ipv4.tcp_keepalive_time=3000
    net.ipv4.tcp_keepalive_intvl=30
    net.ipv4.tcp_keepalive_probes=15
    net.ipv4.tcp_retries2=3
    net.ipv4.tcp_syn_retries=2
    net.ipv4.tcp_sack=0
    net.ipv4.tcp_timestamps=0
    net.ipv4.tcp_window_scaling=0
    # Oracle
    fs.file-max = 6553600
    fs.aio-max-nr=3145728
    kernel.shmmni=4096
    kernel.sem=250 32000 100 142
    kernel.shmmax=2147483648
    kernel.shmall=3279547
    kernel.msgmnb=65536
    kernel.msgmni=2878
    kernel.msgmax=8192
    kernel.exec-shield=0
    # Controls the System Request debugging functionality of the kernel
    kernel.sysrq=1
    kernel.panic=60
    kernel.core_uses_pid=1
    [root@localhost ~]# free | grep Swap
    Swap:      3148700     319916    2828784
    [root@localhost ~]# cat /etc/fstab | grep "/dev/shm"
    tmpfs                   /dev/shm                tmpfs   size=1024M      0 0
    [root@localhost ~]# df | grep "/dev/shm"
    tmpfs                  1048576    452128    596448  44% /dev/shm
    NON-DEFAULT DB PARAMETERS:
    db_block_size        8192
    memory_target          633339904  /* automatic memory management */
    open_cursors         300
    processes            256
    disk_async_io        TRUE
    filesystemio_options SETALL

  • 100% CPU using LabView 7.1 and DSC module

    Seven years ago I used BridgeView and PXI to execute a project, and the results were so good that after that initial system, I installed one more using BridgeView, and three more using LabView 7.1.
    BridgeView is working very well, but lately, LabView 7.1 is giving me more and more problems. It all started in a system running LabView 7.1 and DSC on Windows XP, using a PXI-8187 controller with a PXI-1042 chassis. I have two PXI-6533 digital I/O boards, one PXI-6030E multifunction, one PXI-6713 analog output board, one PXI-6602 counter board and one PXI-8422 serial com. board. In may/06, all of the sudden, the CPU went to a 100% use. Since I am running PID's to control a flash-butt welding machine in a steel factory, this was extremely dangerous. I changed the controller and everything went back to normal. It was running fine until december/06, when the same behavior appeared again. This time changing the controller did not help. We increased the system memory, from 256 MB to 512 MB and everything worked fine. But one month later (january/07) the fault reappeared. This time we changed the chassis and from that moment to this time, we are running smoothly.
    Application problems were suspect from the very first time this problem appeared, but I was unable to identify the source, if any. I used PROFILE VI's and apparently the write/read tags were taking all the processor resources. However, changing the routines and disabling communications, and optimizing CPU intensive programs never solved the CPU overload.
    Until now, I was aware of only one system showing this erratic behavior. But today I went to check another system, with a totally different application. This one is used to measure the thickness of the steel sheet on a rolling mill. Is not so resource-intensive, but the maintenance folks told me that every time they turned off this particular system, they always had problems trying to turn it on.
    I was suspecting of a PLC-communication related issue, but what I found turned my alarms on. I turned off the system, which was fully functional, and turned it back on, and there it was, CPU load at 100%!. Is exactly the same problem that I have on the welder. This system has a PXI-8184, a PXI-1042 chassis, Windows XP, one PXI-6030E, one PXI-6713 and one PXI-6533. I battled for 20 minutes to put the system back in normal conditions.
    I specified every single board, installed everything and programmed all the applications. The BridgeView applications have never showed anything like this. I am using the DSC (Datalogging and Supervisory Control Module) on both applications, and the Lookout Protocol Drivers are communicating to Modicon PLC's.
    Please, I need help to solve this issue. I believe none of your actual Knowledge Base "100% CPU" articles apply to my case...
    Thanks in advance...
    Antonio Jimenez
    [email protected]

    Thanks for your reply...
    Yes, sometimes I have the feeling that the systems works again because some file or database gets initialized after so many reboots.
    Intentionally I turned off all the events and alarm logging to disk. Also the historical data logging is disabled. This is done by code, every time the main VI is started. This was included precisely to save CPU processing power. However, I am communicating to PLC's, and of course I have to declare variables inside the citadel database to make the communication possible.
    Right now I can't have access to the application, because the mill is rolling, but during the next maintenance stop I will check the database location and size, and I could change the directory location the next time the fault comes up.

  • Sessions with Event "class slave wait" taking 100% CPU

    Hi experts,
    I have an issue in an 11.2.0.2 RAC database with 2 standby nodes that are driving me nuts.
    All started when I've been told there are 2 Oracle processes consuming too much CPU in the environment.
    I found 2 processes which takes 100% CPU each. These processes are Oracle processes into the DB and checking them out although they are registered in v$process and v$session, there is nothing related to them in v$bgprocess so I could not find out which oracle processes started these 2 OS processes.
    The view v$session shows them ACTIVE in the event "class slave wait". There aren't too much information about this event, at least I failed to find...
    Using dbms_monitor and dbms_system to create trace events did not create any tracefile. Only ORADEBUG was able to create events but with nearly no information inside the trace files.
    Questions I need to have answered or at least hints that I can follow to find the answer:
    1) what is causing the CPUs to be consumed at 100%? Which process?
    2) Why does these processes are using that much of CPU?
    3) What can be done to safely get over it?
    Honestly I don't know where else to look at except trying to get some help. Could someone give me a hand please?
    BR,
    Lauro Ojeda
    Edited by: LauroOjeda on 26/01/2013 06:44

    Hi Pal, thanks for your reply!
    Here are the answers:
    1. If it is RAC there is no such construct as a "standby node" and you say you have two of them. Please be specific ... is this RAC or Data Guard or a combination? Or do you have a three node cluster with all services pointing to only a single server wasting all of the resources of the other three?
    A: This is a combination of them. We have 2 nodes in a RAC environment shipping logs to two physical standby databases in another site.
    2. Two processes can not be at 100% of CPU any more than I can be 200% awake. Please show us how you arrived at this conclusion, on what hardware and operating system, and include a formatted (read the FAQ to learn how) extract showing what you are seeing.
    A: top in Linux shows two oracle processes consuming 100% (or nearly of it) of 1 CPU each. This is a 16 cores server (each primary node) so 2 of these are working on full capacity to service the described processes.
    3. What processes? Name them and again run a SQL statement and post the output so we can see what you are looking at.
    A: Like I said before I failed to find which background process they belongs to as there are no indications of them in v$bgprocess and in v$session/v$process either. I can see them in v$process and v$session but again, there are no indications of for which bg process they belong to.
    4. Is anything slow? Are there any problems with the system or are you only reacting to two numbers you think are too high?
    A: No, system is not slow because of that but the client wants to investigate and have it sorted as it is not normal.
    Additionally I found a bug in metalink which seems to be the culprit, but I'm unsure yet. This is Bug 12929268 : HIGH CPU ON ORA_O00N PROCESS
    Is any other information that I may provide you?
    Thanks for help!
    Lauro Ojeda

  • Mail Can't Open & com.apple.internetaccount process hogging 100% CPU

    Desperately seeking answers after Mavericks install..
    My mail crashed and now won't open at all. I've tried most (if not all) the suggestions posted by others.  Haven't tried deleting and reinstalling mail yet, as this will be my last resort since I have a work account in it that is not on IMAP.
    And another troubling issue is my macbook's fan is going crazy and feels like its overheating.
    Looking at "Activity Monitor" I see a process "com.apple.internetaccounts" that is taking 100% CPU and 1.6GB of memory!!
    No idea what this process is and can't seem to quit it.
    PLEASE HELP!!! Thanks in advance
    Using EtreCheck, pls see below report:
    Hardware Information:
              MacBook Air (13-inch, Mid 2012)
              MacBook Air - model: MacBookAir5,2
              1 1.8 GHz Intel Core i5 CPU: 2 cores
              4 GB RAM
    Video Information:
              Intel HD Graphics 4000 - VRAM: 1024 MB
    System Software:
              OS X 10.9 (13A603) - Uptime: 0 days 0:11:45
    Disk Information:
              APPLE SSD SM256E disk0 : (251 GB)
                        EFI (disk0s1) <not mounted>: 209.7 MB
                        Macintosh HD (disk0s2) /: 250.14 GB (59.72 GB free)
                        Recovery HD (disk0s3) <not mounted>: 650 MB
    USB Information:
    FireWire Information:
    Thunderbolt Information:
              Apple Inc. thunderbolt_bus
    Kernel Extensions:
    Problem System Launch Daemons:
    Problem System Launch Agents:
              [loaded] com.paragon.NTFS.trial.plist
              [loaded] com.paragon.NTFS.upd.plist
    Launch Daemons:
              [loaded] com.adobe.fpsaud.plist
              [loaded] com.adobe.SwitchBoard.plist
              [loaded] com.microsoft.office.licensing.helper.plist
              [loaded] net.sourceforge.MonolingualHelper.plist
    Launch Agents:
              [not loaded] com.adobe.AAM.Updater-1.0.plist
              [loaded] com.hp.messagecenter.launcher.plist
    User Launch Agents:
              [loaded] com.adobe.ARM.df0ab5bbe6f698196fcc21e3c1e66dcb758bd911f4d637272d9d8109.plist
              [loaded] com.google.keystone.agent.plist
    User Login Items:
              None
    3rd Party Preference Panes:
              Flash Player
              Language Aid
              MagicPrefs
              Paragon NTFS for Mac ® OS X
    Internet Plug-ins:
              AdobePDFViewer.plugin
              AdobePDFViewerNPAPI.plugin
              CMBSecurity.plugin
              Default Browser.plugin
              Flash Player.plugin
              FlashPlayer-10.6.plugin
              JavaAppletPlugin.plugin
              nplastpass.plugin
              QuickTime Plugin.plugin
              SharePointBrowserPlugin.plugin
              Silverlight.plugin
    User Internet Plug-ins:
              aliedit.plugin
              Google Earth Web Plug-in.plugin
              QQMail.plugin
              QQMail.plugin
              txftn.plugin
              RealPlayer Plugin.plugin
              txftn.plugin
    Bad Fonts:
              None
    Top Processes by CPU:
                 100%          com.apple.internetaccounts
                   4%          WindowServer
                   4%          com.apple.WebKit.WebContent
                   2%          EtreCheck
                   1%          Safari
                   1%          Activity Monitor
                   0%          fontd
                   0%          hidd
                   0%          sysmond
                   0%          aosnotifyd
    Top Processes by Memory:
              1.62 GB            com.apple.internetaccounts
              180 MB             com.apple.IconServicesAgent
              143 MB             com.apple.WebKit.WebContent
              111 MB             Safari
              49 MB              Dock
              45 MB              WindowServer
              37 MB              mds_stores
              37 MB              Activity Monitor
              33 MB              Finder
              25 MB              com.apple.WebKit.Networking
    Virtual Memory Statistics
              35 MB              Free RAM
              1.51 GB            Active RAM
              1.48 GB            Inactive RAM
              587 MB             Wired RAM
              252 MB             Page-ins
              840 KB             Page-outs

    @Drewli77 yup that's it. When Mail opened I chose Google/Gmail and let Mail set the account up for me.
    Before doing that I had noticed com.apple.internetaccounts hogging the CPU. I went into System Preferences > Internet Accounts, waited 10 minutes for the spinning ball to stop, then deleted the Google account in there. There was only one Google account in there, despite the fact that I have four Google accounts set up in Mac Mail. Anyway this one account seemed to be what was slowing down that preference pane. After deleting Accounts.plist I re-added my accounts in Mail, which added them to the Internet Accounts preference pane, but now that preference pane (and Mail) open just fine without hogging resources.
    What annoys me is the fact that hitting Delete on a message sends it to Trash, which in Mavericks corresponds to Gmail's Trash, meaning it gets purged every month (regardless of the setting you choose in Mac Mail). I've been using Option-Delete to Archive it, but I wish I could just use Delete for that, since I always Archive and rarely Trash messages. I would set another folder to be used for Trash, but sadly, all of the options under Mailbox > "Use this mailbox for" are greyed out.

  • Photoshop CS5 always around 100% CPU usage

    Photoshop CS5 12.0.1 x64 running on Snow Leopard 10.6.4 always takes around 100% CPU, no matter if it's on screen or not. I can not figure out what it is doing behind the scene. I have deactivated fonts preview and I have no third party plugin except for the FontExplorer plugin (that handles missing font requests).
    Use case example : Right now, Photoshop is hidden and on a different Space (as in Mac "Spaces"). The only open file is a psd file, containg only a few layer and groups, no text and is 240px X 130px. For the past 10 minutes, Photoshop's CPU usage has varied between 99.8% and 103%. This seems odd, comparing to After Effects running at the same time using only around 0.6% CPU...
    Any idea how I can fix this?

    Try turning off font previews, try disabling your third party plugins.
    We've seen several third party plugin bugs that would waste CPU time.
    And font previews can spend time (completely interruptable) until the previews are completed.
    Photoshop normally uses 1% or less CPU when in the background.

  • Mdnsresponder will not quit.  Consumes above 100% CPU and kills my battery.  Also causes my fan to run constantly and my computer to get extremely hot.  Force quitting doesn't work.  It just comes back.

    The mdnsresponder will not quit.  Consumes above 100% CPU and kills my battery.  Also causes my fan to run constantly and my computer to get extremely hot.  Force quitting doesn't work.  It just comes back.   I posted about this earlier and never got an answer.  Somebody, please help. 
    Thanks.

    mDNSResponder is a background process that runs all the time. If you kill it, it's relaunched automatically.
    Please launch the Console application and select "system.log" from the file list. Enter "mDNSResponder" (without the quotes) in the search field. Post a sample of the log messages in the Console window -- only one example of each repeated message, please.

Maybe you are looking for