-
FCP 10.0.3 Memory Issue
I was wondering if anyone else was having a similar issue to what I’m experiencing.
I upgraded as soon as the update came out, and started working on a client project that I’ve been working on for the last couple weeks. FCP updated the old projects and events to the new version, which took quite some time. The project I’m working on is huge; over 50 hours of edited video, and probably 3 times that in source material. However, before the update all three of my workstations seemed to handle it just fine.
When I tried to export one of my projects today via compressor, I waited for over half hour with no progress being made. Eventually, I got a message from Finder telling me that my system drive did not have enough space left on it for application memory (it has over 700 GB out of 1 TB free). I checked the Activity Monitor, and was astonished to find that over 150 GB of virtual memory was being used, and that FCP had over 12 GB of page-outs. Now I know that FCP uses every bit of memory available, but there seems to be an issue introduced in this new version that is causing some kind of infinite loop or something (or perhaps the issue is with my updated project file). I have never seen FCP act this way with this project before the update, and I have now tested it on two different workstations and have had the same result. The bottom line seems to be that I can’t export this project file via compressor, which is a real problem as my client needs a DVD this week.
If anybody else is experiencing this, we need to let Apple know asap so they can fix whatever is causing it.
-
4 Replies
-
A bit of an update: it seems that the problem is not limited to simply trying to export. It happens when I try to load a project into the timeline as well. Looking at the Activity Monitor, what starts happening is the program will quickly eat up all physical memory and then start paging out to virtual memory like crazy, with hardly any page-ins. This seems to go on indefinitely, until I force-quit the program. Meanwhile, FCP is non-responsive (spinning beach ball of death).
I have tested some of my other, smaller projects, and they seem to have updated to the new version just fine. I’m beginning to think that the problem lies with the process of updating my rather large event to the new version. I have tried hiding all but one project file, and that doesn’t fix the problem. This never showed up before the update, so I know it’s not that my computers simply can’t handle the media. I think something is broken and causing a recursive loop when FCP tries accessing media files. That’s my theory, anyway. At any rate, it’s infuriating. At this point I’m going to have to go back to a backup drive on my one computer that hasn’t updated yet and export full-resolution versions of each project, so I can continue working from those in a new event.
-
Having memory issues as well. Flakiest thing since the .3 upgrade: Opened a 1080/29.97 project only to have it look fuzzy. Checked the settings only to find it was now 720/25. Tried to change it back but 720 and 25 were the only “custom” options available. Copied the storyline(s) and pasted them into a new 1080 project and got back to work. Exported…got revisions list….moved the whole thing over to Premiere Pro/AE and put FCPX back on the shelf for another day. I don’t have time/money for this nonsense.
-
What sort of media are you using? Does it load into a “clean” fcp?
I had a problem after the upgrade to 10.0.1 where for some reason it would not read my H624 files generated from a VIO POV.hd and input as linked files.
10.0.0 did read these files , and other makes of H264 did work. ( Motion would not handle them either.)My computer just went into an endless loop when trying to access events (update) with these files.
I could not even run FCX if I had a drive connected that had events with these files.
It also would not import them directly, but had a similar loop crash.Opening a project/events without these files was fine.
In the end I opened the events in 10.0.0 and transcoded all of my media to prores, to use with 10.0.1 .
Apple engineers acknowledged the problem on importing these files then 10.0.2 fixed the problem, perhaps 10.0.3 has problems with similar media?
Steve
-
I found the problem. Apparently, a single .psd file was causing the hang. Here’s my theory: because FCP now is capable of working with Photoshop layers, it has to rasterize each layer separately instead of using the pre-rasterized, flattened image that Photoshop creates. My hunch is that it was getting hung up on a smart filter my .psd was using, causing a recursive loop and thus the memory dump. This would explain why the latest version is the first time this issue has shown up, and also why certain projects seemed to work fine while others didn’t.
So the take-away is, beware of importing Photoshop files, especially with smart filters.
Reply to this Discussion! Login or Sign Up