11 Replies Latest reply: Nov 5, 2013 6:18 PM by Rick Carlton
Rick Carlton Level 1 Level 1 (10 points)

I have a Mid 2011 21" Imac I5 with 8 Gb. of memory installed and a 1 TB drive..

 

All I am usually running is Mail and Safari.  I have been running low on memory lately and also getting the color wheel of death.

 

My activity moitor shows something called kernal task that takes up 700mb, Safari Web Content uses 1.75 GB., Safari uses 450 mb., and I had Safari Flash which was also a big user but I uninstalled it.

 

Are these numbers out of line? It seems like I drain down to less than 300 mb and my memory moniter shows the number in red. I have thought of buying another pair of 4 Gb. chips for a total of 12 but read somewhere that I would lose dual processing.

 

I have leaked down to 1.5 GB since I started typing this.

 

All help appreciated - Rick


iMac, Mac OS X (10.7.5)
  • Linc Davis Level 10 Level 10 (169,380 points)

    Select the System Memory tab. What values are shown in the bottom part of the window for Page outs and Swap used?

  • Rick Carlton Level 1 Level 1 (10 points)

    0 for both.

  • Linc Davis Level 10 Level 10 (169,380 points)

    When you next have the problem, note the exact time: hour, minute, second.

     

    If you have more than one user account, these instructions must be carried out as an administrator.

     

    Launch the Console application in any of the following ways:

     

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

     

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View Show Log List

    from the menu bar.

    Scroll back in the log to the time you noted above. Select any messages timestamped from then until the end of the episode, or until they start to repeat. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).

     

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

     

    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Rick Carlton Level 1 Level 1 (10 points)

    OK - thanks.

  • Rick Carlton Level 1 Level 1 (10 points)

    9/14/13 6:44:40.975 PM McAfee Reporter: Failed to register with FMP

    9/14/13 6:44:40.976 PM com.apple.launchd.peruser.501: (com.mcafee.menulet) Throttling respawn: Will start in 9 seconds

    9/14/13 6:44:41.046 PM com.apple.launchd.peruser.501: (com.mcafee.reporter) Throttling respawn: Will start in 9 seconds

    9/14/13 6:44:41.452 PM com.apple.launchd: (com.mcafee.virusscan.fmpd[13730]) getgrnam("Virex") failed

    9/14/13 6:44:41.452 PM com.apple.launchd: (com.mcafee.ssm.ScanManager[13729]) getgrnam("Virex") failed

    9/14/13 6:44:42.532 PM System Preferences: Cannot call setInetDServiceEnabled:enabled without first being authenticated

    9/14/13 6:44:50.491 PM ntpd: proto: precision = 1.000 usec

    9/14/13 6:44:51.000 PM kernel: System Preferenc (map: 0xffffff8012418d98) triggered DYLD shared region unnest for map: 0xffffff8012418d98, region 0x7fff99200000->0x7fff99400000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

    9/14/13 6:44:52.165 PM com.apple.launchd: (com.mcafee.ssm.ScanManager[13740]) getgrnam("Virex") failed

    9/14/13 6:44:52.165 PM com.apple.launchd: (com.mcafee.virusscan.fmpd[13739]) getgrnam("Virex") failed

    9/14/13 6:44:56.475 PM com.mcafee.reporter: objc[13738]: Object 0x519860 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug

    9/14/13 6:44:56.521 PM Menulet: Menulet : Caught an Exception while Registering with FMP

    9/14/13 6:44:56.521 PM McAfee Reporter: Reporter : FMP exception in ReporterRegisterWithFMP: msg :: connect call failed

    9/14/13 6:44:56.521 PM Menulet: Failed to register with FMP

    9/14/13 6:44:56.521 PM McAfee Reporter: Failed to register with FMP

    9/14/13 6:44:56.570 PM com.apple.launchd.peruser.501: (com.mcafee.menulet) Throttling respawn: Will start in 4 seconds

    9/14/13 6:44:56.637 PM com.apple.launchd.peruser.501: (com.mcafee.reporter) Throttling respawn: Will start in 4 seconds

    9/14/13 6:45:02.633 PM com.mcafee.reporter: objc[13742]: Object 0x561050 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug

    9/14/13 6:45:02.643 PM com.apple.launchd: (com.mcafee.ssm.ScanManager[13744]) getgrnam("Virex") failed

    9/14/13 6:45:02.643 PM com.apple.launchd: (com.mcafee.virusscan.fmpd[13743]) getgrnam("Virex") failed

    9/14/13 6:45:02.743 PM McAfee Reporter: Reporter : FMP exception in ReporterRegisterWithFMP: msg :: connect call failed

    9/14/13 6:45:02.743 PM Menulet: Menulet : Caught an Exception while Registering with FMP

    9/14/13 6:45:02.743 PM Menulet: Failed to register with FMP

    9/14/13 6:45:02.743 PM McAfee Reporter: Failed to register with FMP

    9/14/13 6:45:02.744 PM com.apple.launchd.peruser.501: (com.mcafee.menulet) Throttling respawn: Will start in 8 seconds

    9/14/13 6:44:50.491 PM ntpd: proto: precision = 1.000 usec

    9/14/13 6:44:51.000 PM kernel: System Preferenc (map: 0xffffff8012418d98) triggered DYLD shared region unnest for map: 0xffffff8012418d98, region 0x7fff99200000->0x7fff99400000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

    9/14/13 6:44:52.165 PM com.apple.launchd: (com.mcafee.ssm.ScanManager[13740]) getgrnam("Virex") failed

    9/14/13 6:44:52.165 PM com.apple.launchd: (com.mcafee.virusscan.fmpd[13739]) getgrnam("Virex") failed

    9/14/13 6:44:56.475 PM com.mcafee.reporter: objc[13738]: Object 0x519860 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug

    9/14/13 6:44:56.521 PM Menulet: Menulet : Caught an Exception while Registering with FMP

    9/14/13 6:44:56.521 PM McAfee Reporter: Reporter : FMP exception in ReporterRegisterWithFMP: msg :: connect call failed

    9/14/13 6:44:56.521 PM Menulet: Failed to register with FMP

    9/14/13 6:44:56.521 PM McAfee Reporter: Failed to register with FMP

    9/14/13 6:44:56.570 PM com.apple.launchd.peruser.501: (com.mcafee.menulet) Throttling respawn: Will start in 4 seconds

    9/14/13 6:44:56.637 PM com.apple.launchd.peruser.501: (com.mcafee.reporter) Throttling respawn: Will start in 4 seconds

    9/14/13 6:45:02.633 PM com.mcafee.reporter: objc[13742]: Object 0x561050 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug

    9/14/13 6:45:02.643 PM com.apple.launchd: (com.mcafee.ssm.ScanManager[13744]) getgrnam("Virex") failed

    9/14/13 6:45:02.643 PM com.apple.launchd: (com.mcafee.virusscan.fmpd[13743]) getgrnam("Virex") failed

    9/14/13 6:45:02.743 PM McAfee Reporter: Reporter : FMP exception in ReporterRegisterWithFMP: msg :: connect call failed

    9/14/13 6:45:02.743 PM Menulet: Menulet : Caught an Exception while Registering with FMP

    9/14/13 6:45:02.743 PM Menulet: Failed to register with FMP

    9/14/13 6:45:02.743 PM McAfee Reporter: Failed to register with FMP

    9/14/13 6:45:02.744 PM com.apple.launchd.peruser.501: (com.mcafee.menulet) Throttling respawn: Will start in 8 seconds

    9/14/13 6:45:02.775 PM com.apple.launchd.peruser.501: (com.mcafee.reporter) Throttling respawn: Will start in 8 seconds

    9/14/13 6:45:10.000 PM kernel: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT

    9/14/13 6:45:10.000 PM kernel: macx_swapon SUCCESS

  • Linc Davis Level 10 Level 10 (169,380 points)

    Uninstall the McAfee product by following the instructions on whichever of the pages linked below is applicable:

      
      
    Note that if you have already tried to uninstall the software, you may have to reinstall it in order to finish the job. If you have a different version of the product, the procedure may be different.
      
    Back up all data before making any changes.

  • Rick Carlton Level 1 Level 1 (10 points)

    Thanks Linc -

     

    I figured it out the minute I saw McAfee repeated over and over - uninstalled it before your answer. I didn't know I still had it. Your lesson was a gold mine of info and I thank you very much.

     

    Is there a virus software you recommend?

  • Rick Carlton Level 1 Level 1 (10 points)

    Linc -

     

    One more question. I see you included instructions for Virus scan for 8.6. I am running 10.7.5. Did you see evidence of sommething else that should be removed?

     

    Thanks - Rick

  • Linc Davis Level 10 Level 10 (169,380 points)

    I've never installed the product, and I don't know how to uninstall it.

     

    1. This comment applies to malicious software ("malware") that's installed unwittingly by the victim of a network attack. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
      
    If you find this comment too long or too technical, read only sections 5, 6, and 10.
      
    OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.

    2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user, but internally Apple calls it "XProtect." The malware recognition database is automatically checked for updates once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
       
    The following caveats apply to XProtect:
    • It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
    • It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
    3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
       
    Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
    • It can easily be disabled or overridden by the user.
    • A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
    • An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
    For the reasons given above, App Store products, and other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. OS X security is based on user input. Never click through any request for authorization without thinking.
           
    4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is presumably effective against known attacks, but maybe not against unknown attacks. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
     
    5. XProtect, Gatekeeper, and MRT reduce the risk of malware attack, but they're not absolute protection. The first and best line of defense is always your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the malware attacker. If you're smarter than he thinks you are, you'll win.
        
    That means, in practice, that you never use software that comes from an untrustworthy source, or that does something inherently untrustworthy. How do you know what is trustworthy?
    • Any website that prompts you to install a “codec,” “plug-in,” "player," "extractor," or “certificate” that comes from that same site, or an unknown one, is untrustworthy.
    • A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
    • Pirated copies or "cracks" of commercial software, no matter where they come from, are unsafe.
    • Software of any kind downloaded from a BitTorrent or from a Usenet binary newsgroup is unsafe.
    • Software that purports to help you do something that's illegal or that infringes copyright, such as saving streamed audio or video for reuse without permission, is unsafe. All YouTube "downloaders" are in this category, though not all are necessarily harmful.
    • Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. If it comes from any other source, it's unsafe.
    • Even signed applications, no matter what the source, should not be trusted if they do something unexpected, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
    6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
      
    Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
       
    Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable itnot JavaScript — in your browsers.
       
    Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.

    Follow the above guidelines, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself from malware.

    7. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good, if they do any good at all. Any database of known threats is always going to be out of date. Most of the danger is from unknown threats. If you need to be able to detect Windows malware in your files, use one of the free anti-virus products in the Mac App Store — nothing else.
      
    Why shouldn't you use commercial "anti-virus" products?
    • Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
    • In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
    • By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
    8. An anti-malware product from the App Store, such as "ClamXav," doesn't have these drawbacks. That doesn't mean it's entirely safe. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
        
    An anti-virus app is not needed, and should not be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
        
    A Windows malware attachment in email is usually easy to recognize. The file name will often be targeted at people who aren't very bright; for example:
      
    ♥♥♥♥♥♥♥♥♥♥♥♥♥♥!!!!!!!H0TBABEZ4U!!!!!!!.AVI♥♥♥♥♥♥♥♥♥♥♥♥♥♥.exe
       
    Anti-virus software may be able to tell you which particular virus or trojan it is, but do you care? In practice, there's seldom a reason to use the software unless a network administrator requires you to do it.
      
    The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have the disadvantages mentioned in section 7.
      
    9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
        
    10. As a Mac user you don't have to live in fear that your computer is going to be infected every time you install an application, read email, or visit a web page. But neither should you have the false idea that you will always be safe, no matter what you do. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices.

  • Rick Carlton Level 1 Level 1 (10 points)

    Just an add-on. After I used the McAfee uninstaller I went back to the console because memory still seemed low. I saw continuous McAfee virus searches.

     

    Also, I tried the sudo command and it wasn't recognized.

     

    I shut the whole thing down and restarted - no more virus searches and my memory now steady around 5 Gb free. Seems like the parts remain after uninstall until a restart.

     

    Now happy - so far. Will know more after a long work session.

     

    Thanks again - Rick

  • Rick Carlton Level 1 Level 1 (10 points)

    11/5/13 9:11:14.643 PM Console[4506]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.

    11/5/13 9:13:25.798 PM Console[4511]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.

    11/5/13 9:15:45.213 PM accountsd[4514]: assertion failed: 13A603: liblaunch.dylib + 25164 [FCBF0A02-0B06-3F97-9248-5062A9DEB32C]: 0x25

    11/5/13 9:17:15.788 PM com.apple.IconServicesAgent[3788]: main Failed to composit image for binding VariantBinding [0x1af] flags: 0x8 binding: FileInfoBinding [0x277] - extension: pages, UTI: com.apple.iwork.pages.pages, fileType: ????.

    11/5/13 9:17:15.796 PM quicklookd[4516]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x203] flags: 0x8 binding: FileInfoBinding [0x103] - extension: pages, UTI: com.apple.iwork.pages.pages, fileType: ???? request size:16 scale: 1

     

     

    Same problem repeating - memory leak.