inactive memory grows till no memory left.
Hi there,
I have a new 2.5 Ghz Intel Core i7.
12 GB of ram.
I had this issue on the Capture One 6.3.3 and now on 6.3.4.
I start capture once the mac is on and running, with no other apps on other than finder.
Start a Tethered Session and start shooting.. Have had following issue on, phase backs, nikon and canon.
As we start shooting tethered the real memory usage stays at around 2gb for Capture One, shown on the activity monitor.
The "inactive memory" grows until there is no more memory to chew up and at that stage things slow right down and obviously have to stop shooting. Once things are settled, restarting Capture One and/or restarting the mac resets the inactive memory and free memory count back to normal amounts.
I have not completely uninstalled and reinstalled capture one yet, but will do and see if it happens again.
I tested the memory usage on photoshop and other programs to see if the same thing occurs and it does not.
Its seems I am getting a freak memory leak, but not pretending to know everything about the activity monitor and how memory is used, but any input would be fantastic.
thanks.
J
I have a new 2.5 Ghz Intel Core i7.
12 GB of ram.
I had this issue on the Capture One 6.3.3 and now on 6.3.4.
I start capture once the mac is on and running, with no other apps on other than finder.
Start a Tethered Session and start shooting.. Have had following issue on, phase backs, nikon and canon.
As we start shooting tethered the real memory usage stays at around 2gb for Capture One, shown on the activity monitor.
The "inactive memory" grows until there is no more memory to chew up and at that stage things slow right down and obviously have to stop shooting. Once things are settled, restarting Capture One and/or restarting the mac resets the inactive memory and free memory count back to normal amounts.
I have not completely uninstalled and reinstalled capture one yet, but will do and see if it happens again.
I tested the memory usage on photoshop and other programs to see if the same thing occurs and it does not.
Its seems I am getting a freak memory leak, but not pretending to know everything about the activity monitor and how memory is used, but any input would be fantastic.
thanks.
J
0
-
We saw the same behavior on MacPro towers and MacBook Pro laptops until we switched OpenCL to 'Auto'.
We were running 6.1.1 with OpenCL set to 'Never' and it ran pretty well.
Now with 6.3.4 and OpenCL set to 'Never' we get very unstable behavior and lots of crashes. After shifting OpenCL to 'Auto', not as many issues. Much greater stability.0 -
Also, if you are packing as EIP upon capture, try using the native RAW file format instead for capturing. You could go back and pack as EIP later. 0 -
So I have re installed completely, and done tests with both the OpenCL on never and Auto, both having the same issue.
Its a slow leak, whether Im shooting teathered or browsing the pics. It starts to chew up memory until there is no more to chew. So would be around 10-15mins of the computer working pretty hard before Im running on 20mb of free memory. Then everything slows down. (does anyone else have this issue?) Is it just the fact that you can only do so much shooting on a laptop before all its resources are used and you have to stop? With the new macbookpro, I would think it would be able to handle more than 15mins of browsing or shooting, no?
I have downloaded a little app called "free memory", that I am now using in between shots to free up the inactive memory.
Not to sure where to go from here, only happens on the capture one software.
any input will be highly appreciated.
thanks
Jonathan0 -
we are using MacPro towers and when we switched to OpenCL 'Auto' Capture One seemed to use RAM much more efficiently.
I wonder if your issue is related to the MacBook Pro's dual graphics cards? Have you tried switching the system preference to use only the high quality graphics card? It would affect battery life but worth a try.
Try a google search of 'disable MacBook Pro graphics switching' and see if there is a fix for your OS.0 -
I have a similar problem, all the time, with my 2008 mac pro and 18 GB ram.
During a day's shooting with p25 tethered, I usually restart the computer around at lunch time before the inactive ram grows too much. My typical capture folder size per day is around 20GB. And the whole day of shooting is smooth.
I think that somehow the inactive ram grows and the computer becomes slow when there is no free ram...
I usually don't use_open Photoshop or any other softwares except Mail, while shooting tethered. When I must use Photoshop, I make sure that the software doesn't use too much ram through adjusting the photoshop_preference. Also, I rarely use the "session favorites" feature in Capture One software.0 -
Same issue.
Mac/Unix nerds say that it's not possible.
My solution is FreeMemoryPro out of the app store.
Give it a minute and it's back and the system stays stable.
Peter0 -
Hi all,
there is no need to buy an app to recover the inactive memory.
Just install the Apple CHUD (Computer Hardware Understanding Developer) Tools.
Open a terminal and run purge .
$ purge
$
Be patient it might take a short while, depending on your amount of inactive memory, until the command prompt is back.
The inactive memory is now reverted to free memory.
Michael0 -
Does this happen only when you are shooting tethered ?
Sounds like there C1 is capturing the image to a block of memory then not releasing it when the image is saved.0 -
i have the same issue
mbp 17 8gb ram ssd drive for system and 7200 for storage.
i downloaded "libera memory" (free software) and it helps a lot
cheers paolo0 -
Another way to free up inactive memory on OS X is the terminal command 'purge'. purge
This command is part of OS X and does not need any software installation. It takes a few seconds, and you can monitor the results immediately in Activity Monitor.0 -
thanks a lot paul, your advices ar always precious! 0 -
Hi Paul,
is this right?
(from terminal):
" select all
> purge
-bash: syntax error near unexpected token `purge' "0 -
[quote="dale11833" wrote:
Hi Paul,
is this right?
(from terminal):
" select all
> purge
-bash: syntax error near unexpected token `purge' "
Not sure what happened (or went wrong). Just type purge after the terminal prompt, do not copy/paste from this site; that might not work with Terminal.
HTH0 -
i opened terminal and typed purge says command not found
purge
-bash: purge: command not found0 -
[quote="dale11833" wrote:
i opened terminal and typed purge says command not found
purge
-bash: purge: command not found
What version of OS X are you running? I used it on 10.7.3.0 -
Hi Paul,
I am on 10.6.80 -
hi dale11833,
I was a bit optimistic when stating that the purge command is onboard OS X by default. It is for Lion but for Snow Leopard you need to install the Xcode tool from your DVD (based on looking around on the inter webs, not tested).0 -
Thanks for that info Paul 0 -
A good article on the matter, in particular the section at the end:
http://reviews.cnet.com/8301-13727_7-57 ... ory-usage/0 -
Free Memory Pro from the Apps store helps no end, if you have 8Gb of ram on your machine
set the warning level to 1000mb & make sure Smart Auto Free is checked in the prefs, then you
don't have to keep restarting C1… a drag but it seems to work...0 -
I had the same issue last week running 6.4 on Lion. Had been on 2 day shoot and around lunchtime of the second day Capture One slowly ground to a halt.
When importing images I was being told 15 min to import a few gig, the previews were taking forever to render (like one every 20 seconds). I created a new session and imported the RAW images (without any settings), same problem. Restarted, same problem. Deleted Capture ones cache, plist etc, same problem. Ran applejack, PRAM reset - same problem. Completely reinstalled Capture One, same problem.
During this time the inactive memory was taking up well over half of the pie chart, and worryingly restarting didn't work as once capture one reopened the same memory problems occured. Had to switch to new laptop, which serves as a warning never go on location without one.
I'm going to install XCODE on all machines I work on when working on big productions from now on, but am baffled why the laptop seemed to be working fine for a day and a half and then just stopped refreshing memory and restarts failed to solve the problem...0 -
Many years on there are still similar probems on Windows 10. Importing a large catalogue the amount of RAM grabbed by capture One increases until the machine crashes (Black Screen of Death). Whether due to preview generation or some other part of the application I cannot sayt.
But it has all the signs of a serious memory leak (AKA Incompetent programming! If you want then I will share some of my 40 years programming experience with whoever is responsible for such a mess. Do you actually test any realistic scenarios? It does not look like it)
It is about time these serious bugs were fixed, instead of wasting time adding more and more features. It is like adding a fancier stero or a cup holder to a car that breaks down every few miles.
0
Post is closed for comments.
Comments
22 comments