Apple Event: May 7th at 7 am PT

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

com.apple.photomodel uses 38GB real memory or 198GB virtual memory even after Photos closed on High Sierra

I didn't have a hope that the Photos app on OS X would use less memory because I have a hope that macOS Sierra would have fixed the memory management for the Photos app. I was wrong. Then I have a "High" hope that macOS "High" Sierra should eventually fix the memory black hole but should I have that hope?


Today I ran Photos app on macOS 10.13 with Supplementary Update. After a while, I walked on the keyboard like walking on swamp. Every character came out on the i7 7700K iMac not within a minute. I opened the Activity Monitor, and 38GB out of 40GB were used. The com.apple.photomodel process even takes up to 198GB of memory and 99% of CPU, three hours after I quitted Photos app which I let it run for 4 hours doing nothing else on the iMac.


Memory Clean 2 in Extreme Clean mode claims back 2 GB only.


Is it because of the Hunger Games, Big Data being collected or Machine Learning mode of the Photos app Version 3.0 (3201.11.120)?

iMac, macOS High Sierra (10.13), iMac 2017 5K 27-inch 4.2GHz i7 40GB

Posted on Oct 15, 2017 10:12 PM

Reply
19 replies

Oct 17, 2017 5:15 AM in response to John Galt

Your reply is totally irrelevant to my question. I'm asking about the anomalies of Photos app on macOS.

Besides, Memory Clean (now, Memory Clean 2) helps a lot in releasing memory on MBA. Your comment "Using junk..." is your personal opinion. In my experience with Memory Clean, I have never come across anything from it "preventing" my Mac from working properly. So, you're welcome to substantiate with evidence about "prevents your Mac from working properly".


Even without loading Memory Clean (or Memory Clean 2), the Photos app still have the same problem. So, if you have any insight about Photos app problem itself alone, welcome to inspire me.

Oct 17, 2017 6:18 AM in response to Ivan H

Use Activity Monitor to force quit the memory hogging process. Something went wrong with that. It should restart automatically and not use such an inordinate amount of memory.


Using programs like memory clean does not solve problems like this and can prevent your system from working as designed. Since Mavericks the OS handles memory allocation and reuse in such a way that programs like this one (which try to force the purging of “inactive” memory) actually DECREASE system performance. There was a time when such programs were marginally useful. Now they should NOT be used.

Oct 17, 2017 6:25 AM in response to Ivan H


Ivan H wrote:


...Besides, Memory Clean (now, Memory Clean 2) helps a lot in releasing memory on MBA. Your comment "Using junk..." is your personal opinion. In my experience with Memory Clean, I have never come across anything from it "preventing" my Mac from working properly. So, you're welcome to substantiate with evidence about "prevents your Mac from working properly".



If you need to substantiate with evidence then uninstall the App and see what OS X is telling you without the junk-ware interfering with the OS. If you need more evidence you can search the forums here and see where junk like Memory Clean and dozens of other products; many of which are sold on the App Store are the first offenders with system destabilization and when they are removed problems go away.


For futher analysis you may post an Etrecheck report. The link is http://www.etrecheck.com

Oct 17, 2017 4:04 PM in response to Ivan H

Do as you please, but using totally worthless garbage products like "memory clean" will only exacerbate whatever the problem may be, if there is one, which is questionable. macOS manages its memory resources to obtain maximum performance. Interfering with it can only degrade performance and accelerate hardware failure.


Rule 1 of Macs is don't install junk. Those things don't fix problems. They cause them. Good luck!

Oct 18, 2017 1:14 AM in response to John Galt

A lot of uni students use those "junk" products because their MacBook Airs have 4GB/8GB and while doing research requires a lot of documents stay open. The garbage collection (of memory) of OS X is famously bad! That gives the Memory Clean or similar products a niche to survive. Memory Clean worked very well in the past. It's upgraded version of Memory Clean 2? Not bad, from empirical experience.

Oct 18, 2017 5:52 AM in response to Ivan H

I don't know why photomodel would be using such much memory. It is indeed excessive.

BUT... note that most of it is compressed.

That IS the memory management of macOS doing its work.

Otherwise you would need more than 200GB of swap space.

Stuff like memoryclean have no notion of compressed memory.

Compressed memory is much faster to retrieve than if it had been swapped to disk instead.

CPU (needed to compress and decompress) and RAM are orders of magnitude faster than the SSD (and HD is yet an order of magnitude slower than SSD, as we all know).

Oct 18, 2017 6:11 AM in response to Luis Sequeira1

It’s too expensive for a 3TB SSD/Flash storage. I guess the photosmodel process is using ML (machine learning) to do something like unsupervised learning from my photos’ library. The ML Library has a lot of room for improvement, or it’s too ambitious to be part of the Photos app.

where is the promised “memory slicing” technology mentioned in WWDC?

Oct 18, 2017 12:41 PM in response to Ivan H

Ivan H wrote:


A lot of uni students use those "junk" products because their MacBook Airs have 4GB/8GB and while doing research requires a lot of documents stay open. The garbage collection (of memory) of OS X is famously bad! That gives the Memory Clean or similar products a niche to survive. Memory Clean worked very well in the past. It's upgraded version of Memory Clean 2? Not bad, from empirical experience.


The predictable abundance of ignorant, gullible consumers gives the Memory Clean or similar products a niche to survive. It's a multi-billion dollar industry, and you are its ideal customer.

Oct 18, 2017 2:06 PM in response to Ivan H

Ivan H wrote:


Btw, I think compressed memory used 28GB of physical memory, 244GB compressed memory were swapped to the slow Fusion Drive.


No, 244GB compressed memory means that a portion of memory worth 244GB, and which not being actively used by the application, is compressed to save space.

The compressed version is stored in memory whenever possible.

For example, looking at Activity Monitor right now the total of my Compressed Memory column is a few GB, and Swap Used is only 200MB.


The idea is that compressing and decompressing is much faster than swapping.

Oct 19, 2017 3:38 AM in response to Ivan H

In the illustration of my screenshot above, the swap used was 49.91GB! Memory used by the com.apple.photomodel was 38GB and left no space for other apps / processes to run.


No dispute to the fact that 49.91GB of swap is huge, and 288GB of RAM is huge, and should NOT normally happen.


Now that a few days have passed, I imagine you have force-quit the wayward process, so the question is: does it recur? Or was it a one-off thing that went haywire?

Nov 24, 2017 6:37 PM in response to Luis Sequeira1

Observed for a month and I believe it's the unsupervised machine learning algorithm that analysing my newly imported photos and matching them with those in the library. Leave the Photos app on Mac run overnight or even days, eventually, the memory would be released. Perhaps the process needs an A11X processor rather than an intel i7 4 cores 4.2 GHz!

com.apple.photomodel uses 38GB real memory or 198GB virtual memory even after Photos closed on High Sierra

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