Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Photos app causing very high cpu usage

I updated to photos yesterday, and have been seeing some ridiculous CPU numbers, and my macbook pro is running really hot.

When photos is open I see CPU usage of 200-250% by photos, and another 20-30% by a photoslibrary process. The processor

overheats and reboots the machine. Now I can't run the machine for more than 3 minutes with photos running, without a

freeze-reboot due to heat.

Any ideas what is causing this or if it's a newly discovered bug?

Ralph

MacBook Pro (15-inch, Early 2011)

OS X Yosemite (10.10.3)

2 GHz Intel Core i7

8 GB 1333 MHz DDR3

AMD Radeon HD 6490M 256 MB

960 GB SSD

MacBook Pro, OS X Yosemite (10.10.3)

Posted on Apr 9, 2015 11:36 PM

Reply
93 replies

Apr 11, 2015 12:18 AM in response to spurge b3

"I am also having the same issue with the CPU causing my MAC Book Pro to run very hot. This is after upgrading to the new Photo App this morning. It's something wrong with the update."


Upgrading your library to the Photo app is only the first step. After the conversion is done, silently, the Photo app performs 'face' recognition on all of your photos - that's what causes your MBP to run very hot. If you have a large photo library it can take several hours to process all the photos. Photos does not tell you its doing this so its appears to be a bug.


The easiest way to test this is by creating a iPhoto library with 10 photos in it. Then convert it with Photos app. Wait 15 minutes or so, then you'll notice that the 'faces' icons will appear and the CPU goes back to normal. Like I said, my library with 5000 (20 mp) photos took several hours. I'm not syncing to iCloud yet, but I imagine that will only extend the time required.


The Photos app is designed to tap all of your CPU and the main GPU. So it will take all the processing power you have to perform the conversion.


EDIT: Like I said, my library with 5000 (20 mp) photos took several hours --> on a 2013 MBP 15" (4-core i7) with 16GB RAM and 1GB GPU.

Apr 11, 2015 3:57 AM in response to James Saldana

I'm quite sure the Photos app is supposed to work that way....using all cores, but it shouldn't heat up and shutdown my MacBook Pro.

I have other Pro apps that also consumes lots of CPU when rendering or doing other heavy lifting, but so far Photos is the only app

misbehaving like this.


Yes I did all the usual Disk Utilities routine....even zapped the PRAM and Photos is the only one still misbehaving.


As a workaround I'll update my iMac and copy my iPhoto Library on there so Photos on the iMac can finish up with whatever it needs

to do and copy the Photos Library back to my MacBook Pro.

Apr 11, 2015 4:31 AM in response to ralphcw

"I'm quite sure the Photos app is supposed to work that way....using all cores, but it shouldn't heat up and shutdown my MacBook Pro."


Its normal for the computer to "heat up" is its being fully utilized. Its not normal for it to shutdown since the CPU should throttle itself to stay within safety limits.


"I have other Pro apps that also consumes lots of CPU when rendering or doing other heavy lifting"


Not all Pro apps utilized multiple cores and the GPU in the same way. Comparing one to the other doesn't really prove anything either way.


You should have a crash report of a kernel panic if your Mac restarted. Normally on crash or restart your Mac will alert you to the problem. You can look up the crash report by opening the Console app in the utilities folder.


Open Console and go to the left panel. There you'll find "Files" > "~Library/Logs" > "CrashReporter".

http://www.macobserver.com/tmo/article/mac_os_x_using_console_to_troubleshoot_pr oblems


Then look up the date and time of the crash. It may give an app's name or a general error report.

Apr 12, 2015 12:32 PM in response to James Saldana

@James Saldana thanks for the info.


The "faces" detection is quite honestly dumb, and I consider it a bug. First of all, I don't want it to detect faces - I have no use for that feature. And secondly, it should follow good UX design practices - show that it's doing this, and have a way to stop it.


It did not take all that long on my MBP15" i7 - but it is both unusual and annoying when the fans come on at full speed so they should have taken that into consideration. 23,000 Photos, about 10 minutes.

Apr 12, 2015 12:48 PM in response to Nikolaus Heger

Nikolaus Heger wrote:


@James Saldana thanks for the info.


The "faces" detection is quite honestly dumb, and I consider it a bug. First of all, I don't want it to detect faces - I have no use for that feature. And secondly, it should follow good UX design practices - show that it's doing this, and have a way to stop it.

The «detect faces» feature will also, as a bonus bug so to speak, make your photos library balloon in size, as it creates a cropped copy of each and every photo where it detects a face. In fact, it may make your Mac nearly unusable in the process if you don't have enough disk space.


Well done, Apple. Very well done.

Apr 12, 2015 8:11 PM in response to Nikolaus Heger

Nikolaus Heger wrote:


@James Saldana thanks for the info.


The "faces" detection is quite honestly dumb, and I consider it a bug. First of all, I don't want it to detect faces - I have no use for that feature. And secondly, it should follow good UX design practices - show that it's doing this, and have a way to stop it.


It did not take all that long on my MBP15" i7 - but it is both unusual and annoying when the fans come on at full speed so they should have taken that into consideration. 23,000 Photos, about 10 minutes.


I agree with your comment regarding UX design practices. Apple should have given some indication that post-processing is required after the library has been converted. But that does not make it a bug, rather an unwanted feature. I'm also not sure that 'face' dedication is the only function Photos is performing during post-processing of library. I suspect some kind of optimization is also occurring.


The fans running at full speed is also not a bug. Many professional apps will run the fans at full speed if maximum CPU/GPU output is required for an extended period of time. That's the point of having fans.

Apr 12, 2015 8:22 PM in response to Philbee

Philbee wrote:


Nikolaus Heger wrote:


@James Saldana thanks for the info.


The "faces" detection is quite honestly dumb, and I consider it a bug. First of all, I don't want it to detect faces - I have no use for that feature. And secondly, it should follow good UX design practices - show that it's doing this, and have a way to stop it.

The «detect faces» feature will also, as a bonus bug so to speak, make your photos library balloon in size, as it creates a cropped copy of each and every photo where it detects a face. In fact, it may make your Mac nearly unusable in the process if you don't have enough disk space.


Well done, Apple. Very well done.


I agree. Face detection processing should be an option in Photos but was it an option in iPhoto?

It doesn't appear to have much affect on disks space. My largest library actually dropped by 10GB and a smaller library only gained 300MB. As I said in a previous comment, I suspect some kind of optimization is also being performed along with the 'face' detection during post processing. Possibly the thumbnails? That can take quite a while.

Do yo have a library that increased significantly in size?

Apr 12, 2015 9:15 PM in response to MRYFLYGUY

MRYFLYGUY wrote:


Faces is optional in iPhoto. It can be activated, or not.


Where is that option in iPhoto?


Technically, its also an option in Photos but Photos pre-processes your photos wether you choose to activate the feature or not. I think iPhoto also handled it this way but when you moved your photos from iPhoto to Photos, it reprocessed them all over again because Apple improved 'face' dedication method in Photos.

Apr 12, 2015 10:32 PM in response to James Saldana

In iPhoto, OPEN A PHOTO with a face, select VIEW>INFO from the File menu. Note the "Faces" drop down window in the info screen. By toggling the "Faces" window open, you'll notice it displays an "Unnamed" bubble over the folks in the picture. If you toggle the "Faces" window closed, you'll notice the "Unnamed" bubble goes away. Just close the "Faces" window and you won't be bothered again.

Apr 12, 2015 10:41 PM in response to MRYFLYGUY

MRYFLYGUY wrote:


In iPhoto, OPEN A PHOTO with a face, select VIEW>INFO from the File menu. Note the "Faces" drop down window in the info screen. By toggling the "Faces" window open, you'll notice it displays an "Unnamed" bubble over the folks in the picture. If you toggle the "Faces" window closed, you'll notice the "Unnamed" bubble goes away. Just close the "Faces" window and you won't be bothered again.


Yes, but does that disable the processing of 'faces' for iPhotos? I don't think it does. In Photos the pre-processing seems to be automatic wether you opt to use the feature or not. If you choose to use the feature in Photos under 'Faces' you'll notice that the 'faces' have already been processed.


How to turn off Faces in iPhoto

http://alvinology.com/2014/11/04/how-to-turn-off-faces-in-iphoto/

Apr 12, 2015 10:52 PM in response to snappir

snappir wrote:


Not to worry, after couple of days it settles down to less than zero.


Yep, that's true.


Unfortunately, the silent nature of the processing after conversion of the library is processor intensive and takes a long while, which leads people to believe it's a bug. This is true even with very powerful machines since Photos is now having to re-process photo collections built up over years, unlike iPhoto which only needed to process photos as they were added over time.


Apple should either provide an option to turn 'faces' processing off or at least show some kind of process bar to indicate what it is doing.

Photos app causing very high cpu usage

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.