-
kernel_task maxing out at 2 GB
I have a project that I’m loading in FCP 6 and when it starts to open, the kernel_task process jumps up to 1.97 GB of Virtual Memory. It takes the project well over 5 minutes to load and it’s not trying to access the RAID, it’s just thinking. It then runs okay after loading, but everything gets unstable and starts crashing if I load up Motion too which sucks up the rest of my real RAM. I’m running on a dual 2.7 w/ 5.5 GB of RAM.
Does anyone know of a hack to alter the max kernel_task VM? I found the following but it appears to be specific to Server:
https://docs.info.apple.com/article.html?artnum=305167 -
2 Replies
-
How large is the project file you’re working with?
Jerry
-
The project file itself is 2.6 MB, and the Capture Scratch for it is 59 GB, but I stripped a lot of the media out and saved a new project w/ the same lagging results. I checked on restart, and it looks like before I even open FCP my kernal_task is 1.97 GB VM, and my overall VM is 11 GB. After loading the project, my VM goes up to between 13-14 GB. And as long as I don’t load the .motn clips in my timeline, I’m okay w/ physical RAM and I’m not constantly crashing. So, maybe it’s nothing to do with the kernel_page at all, although it seems like it shouldn’t be maxed out on 2 GB. Can someone check their kernel_page VM size on a fresh restart in the Activity Monitor? Maybe I have a driver conflict?
If it’s not that, then it’s just that ProRes is not only not capturable w/ G5s, it’s also not very useful for editing at all. I have a ProRes HQ 720 24p file laid out in a ProRes HQ 720 60p timeline. The file is only 1 track for 2.5 minutes – it’s all chopped up w/ some clips being .motn files for motion blur and match moving, and the rest w/ 3 way CCs and SmoothCam. Is anyone else having load times of several minutes for ProRes based projects on G5 systems?
Reply to this Discussion! Login or Sign Up