Etrecheck scan - items listed as 'killed'

Linc thinks he should be the only user on these forums who should have and use "special" scripts and tools to use to troubleshoot users Macs.

A very elitist and selfish attitude, as far as I am concerned.

Unless you can provide official copyright or patent on your methods, and direct infringements, such as they are, plagariize is a pretty harsh accusation to make.

At least Etresoft's program provides useful data at a glance versus your methods that produces a long, lengthy and pedantic "piano roll" of data that most of us here really don't want our spend volunteered time plowing through for answers.

If this is really bothersome for you, why don't you simply leave these forums and find other Mac related forums to continue to impart your considerable Mac knowledge to instead of constantly belittling others who welcome other users methods and help by providing such trouble shooting tools that aren't costing anyone anything and are provided and developed by others at no to other users cost and NO profit to themselves.

Drop the attitude! Enough is enough, already!

And for the record, I know plenty about Macs, Mr.Davis, but I won't be spending much more of my lifetime continuing to reach for the top of this support communities' reputation pyramid.

The item you found on the clipboard was the screen shot. It should have been automatically saved to the desktop (the default location) as the .png file you sent to dropbox.com. From there, you can just drag/drop it into a reply here. A green box will appear as you're dragging an image in to show where it will be placed.

Like this:

Let go of the mouse, and the forums will upload and place the image:

This is what I said .... "That's something I just don't know .......... unless it's Dropbox itself!

Yes, I did see that earlier, but I'd never heard of an app named Dropbox until I ran across it just a few minutes ago. I thought you were referring to the Drop Box folder that's in every user account.

Yes, the blue links do work, but once you stop Dropbox from redirecting your screen shots to the clipboard, you'll be able to just post them directly in the forums. Much easier. Your latest post has two spots where some sort of image is likely supposed to be displayed, but both are just showing a spinning wait icon.

Hi there. I'm having the same problem with a VERY SLOW running Macbook Pro. I ran the EtreCheck (below). I've had the comp for about 2 years and it ran ok at the start, but started slowing down a lot within the first 6 months or so. It was still bearable. I upgraded to Yosemite in October which I can't say helped matters much but it had been very slow before already.

It lags when doing pretty much any task... opening from sleep takes a long time. Performing simple tasks lags, regardless of the applications i'm in. Certainly finder is very slow. I haven't tried too many things as I'm not very well-versed technically but running disk utility and repairing permissions seems to help very temporarily. I'm aware that I could upgrade my ram from 4 to 8GB (or maybe even 16GB) but I don't run any large applications (iPhoto is the biggest one probably) so I doubt the lack of RAM could be the only problem, especially since it was running so slow even before Yosemite.

DEVICE DETAILS:

Device: Macbook Pro 13" (mid 2012)

2.5 GHz Intel i5

4GB RAM

Running Yosemite 10.10.1

When I check Activity Monitor (during very laggy moments) it shows using a lot of the RAM but not a ton of pressure.

I had read a couple of posts where people had similar problems and others suggested they run an EtreCheck and upload the report. In some cases members were able to identify problems, so i ran that just in case. It's below.

I'd really appreciate any help you can offer.

Thanks!

EtreCheck version: 2.1.6 (109)

Report generated January 23, 2015 at 12:52:31 AM PST

Download EtreCheck from http://etresoft.com/etrecheck

Click the [Support] links for help with non-Apple products.

Click the [Details] links for more information about that line.

Click the [Adware] links for help removing adware.

Hardware Information: ℹ️

MacBook Pro (13-inch, Mid 2012) (Technical Specifications)

MacBook Pro - model: MacBookPro9,2

1 2.5 GHz Intel Core i5 CPU: 2-core

4 GB RAM Upgradeable

BANK 0/DIMM0

2 GB DDR3 1600 MHz ok

BANK 1/DIMM0

2 GB DDR3 1600 MHz ok

Bluetooth: Good - Handoff/Airdrop2 supported

Wireless: en1: 802.11 a/b/g/n

Battery Health: Normal - Cycle count 200

Video Information: ℹ️

Intel HD Graphics 4000

Color LCD 1280 x 800

System Software: ℹ️

OS X 10.10.1 (14B25) - Time since boot: one day 7:14:0

Disk Information: ℹ️

APPLE HDD TOSHIBA MK5065GSXF disk0 : (500.11 GB)

EFI (disk0s1) <not mounted> : 210 MB

Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB

Macintosh HD (disk1) / : 498.88 GB (287.40 GB free)

Core Storage: disk0s2 499.25 GB Online

HL-DT-ST DVDRW GS31N

USB Information: ℹ️

Apple Inc. FaceTime HD Camera (Built-in)

Apple Inc. BRCM20702 Hub

Apple Inc. Bluetooth USB Host Controller

Apple Inc. Apple Internal Keyboard / Trackpad

Apple Computer, Inc. IR Receiver

Thunderbolt Information: ℹ️

Apple Inc. thunderbolt_bus

Gatekeeper: ℹ️

Mac App Store and identified developers

Problem System Launch Agents: ℹ️

[killed] com.apple.CallHistoryPluginHelper.plist

[killed] com.apple.CallHistorySyncHelper.plist

[killed] com.apple.cmfsyncagent.plist

[killed] com.apple.coreservices.appleid.authentication.plist

[killed] com.apple.EscrowSecurityAlert.plist

[killed] com.apple.printtool.agent.plist

[killed] com.apple.recentsd.plist

[killed] com.apple.scopedbookmarkagent.xpc.plist

[killed] com.apple.telephonyutilities.callservicesd.plist

9 processes killed due to memory pressure

Problem System Launch Daemons: ℹ️

[killed] com.apple.awdd.plist

[killed] com.apple.ctkd.plist

[killed] com.apple.icloud.findmydeviced.plist

[killed] com.apple.ifdreader.plist

[killed] com.apple.nehelper.plist

[killed] com.apple.nsurlsessiond.plist

[killed] com.apple.tccd.system.plist

[killed] com.apple.wdhelper.plist

8 processes killed due to memory pressure

Launch Daemons: ℹ️

[loaded] com.adobe.fpsaud.plist [Support]

[running] com.fitbit.galileod.plist [Support]

User Launch Agents: ℹ️

[loaded] com.google.keystone.agent.plist [Support]

User Login Items: ℹ️

iTunesHelper Application (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

Google Drive Application (/Applications/Google Drive.app)

Google Chrome Application (/Applications/Google Chrome.app)

Fitbit Connect Menubar Helper Application (/Applications/Fitbit Connect.app/Contents/MacOS/Fitbit Connect Menubar Helper.app)

Internet Plug-ins: ℹ️

Silverlight: Version: 5.1.20513.0 - SDK 10.6 [Support]

FlashPlayer-10.6: Version: 16.0.0.257 - SDK 10.6 [Support]

Flash Player: Version: 16.0.0.257 - SDK 10.6 Mismatch! Adobe recommends 16.0.0.287

QuickTime Plugin: Version: 7.7.3

Default Browser: Version: 600 - SDK 10.10

3rd Party Preference Panes: ℹ️

Flash Player [Support]

Time Machine: ℹ️

Time Machine not configured!

Top Processes by CPU: ℹ️

20% installd

7% WindowServer

5% com.apple.WebKit.Networking

2% Safari

2% hidd

Top Processes by Memory: ℹ️

159 MB installd

120 MB mds_stores

107 MB com.apple.WebKit.WebContent

69 MB Finder

64 MB soagent

Virtual Memory Information: ℹ️

57 MB Free RAM

1.65 GB Active RAM

1.59 GB Inactive RAM

749 MB Wired RAM

15.14 GB Page-ins

385 MB Page-outs

Diagnostics Information: ℹ️

Jan 21, 2015, 05:41:41 PM /Users/[redacted]/Library/Logs/DiagnosticReports/cloudd_2015-01-21-174141_[reda cted].crash

Jan 21, 2015, 05:39:12 PM Self test - passed

Those red entries are a side effect of new behaviour in Yosemite. Before Yosemite, under low memory conditions, the system would swap the memory used by inactive processes to disk. For certain system processes, Yosemite will instead just kill them. In theory, the new method in Yosemite should result in a faster system because it isn't swapping to disk as much. In practice, more people are complaining about slowdowns in Yosemite than they did with previous OS versions - or at least it seems that way to me.

In one way, I like this new behaviour because it allows EtreCheck to show problems that have occurred in the past, but are not actively happening. Before Yosemite, we had to look at the page outs value to see if the system had been running out of RAM. Whether or not someone has adequate RAM depends on the software they use. Photoshop, for example, is very greedy about memory. These "killed" processes are not evidence that there is anything wrong with the system. That is the way it is supposed to work. What is wrong is that such EtreCheck reports come from people who are complaining about slowness with Yosemite that they had never experienced before. It is the slowness that is the problem, not the red "killed" entries.

It is leading me to believe that 4 GB RAM may be inadequate for Yosemite. Otherwise, people's machines would be running better under Yosemite and they wouldn't have started posting all of these EtreCheck reports with these "killed" processes.

The most important thing to remember about EtreCheck is that it should be accompanied by a good description of the problem you are experiencing. It should also not be abbreviated in any way. Any particular entries in "red" may not have any meaning. EtreCheck is designed to provide a snapshot of your entire system. I am not particularly happy about the way people focus on the "red" entries. They are almost never the problem, just symptoms. In most cases, entries in green are the ones causing the problem. If anyone has any suggestions about a better way to approach this, I would love to hear it. At the the red gets people worried enough to ask about it. Then, other people here on Apple Support Communities can read the report and identify any real problem if they exist.

In your case, I see no major problems. My biggest concern would be SMC Fan Control. OS X generally doesn't need help from any "memory clean", "clean up", or antivirus tools. Anyone installing one of those tools is likely to make the machine run worse, not better. SMCFanControl does fall into that category. The "red" entries will slowly go away on their own as processes are automatically restarted on demand. If you are experiencing a specific problem, then start a new thread about that problem and include an EtreCheck report to provide basic information about your system. That report might also include some "green" items like "clean up" or antivirus software that are most likely the cause of any such problem.

Please describe the problem, if you have one, in as much relevant detail as possible. The "etrecheck" fad hasn't made that step any less necessary. The usual results of posting etrecheck output on this site without a full description of the problem are very poor.

The many "failed" or "killed" warnings that etrecheck sometimes spews are not a reason to reinstall the OS.

The better your description of the problem, the better the chance of a solution.

For example, if the computer is slow, which specific actions are slow? Is it slow all the time, or only sometimes? What changes did you make, if any, just before it became slow? Have you seen any alerts or error messages? Have you done anything to try to fix it? Most importantly, do you have a current backup of all data? If the answer to the last question is "no," back up now. Ask if you need guidance. Do nothing else until you have a backup.

Please post the whole Etrecheck report.

It''s possible your Mac has insufficient amount of RAM.

2 GBs or less amount of RAM is not enough to efficiently run newer versions of OS X and, specifically, OS X Yosemite.

Obviously, you don't need "etrecheck" to tell you how much RAM you have. You can find that out from the About This Mac box in the Apple menu. In fact, "etrecheck" is incapable of telling you anything that you couldn't easily find out without it.

There are two things I don't like about it. One is that it's an attempt to plagiarize the methods I use on this site, and not a very good one at that, from what I've seen. The other is that it has encouraged people who are unqualified to give technical advice to think that they can now do so, with really dismal results.