Final Cut Pro X export fails! Missing RAM vtdecoderxpcservice

Hi Everyone I have the same issue.

I Have a Sony a7s III and use the codec xavcs 4k 4:2:2 10 bit, my Mac is Apple M1 Max with 64gb of ram

After many test I understood that the problem come out when you have many short clips on a long time line like 15-18 min.

Shorter are the clips faster the VTDecoderXPCService burn memory. After "memory used" reach 62-64 gb "swap used" start go up and when reach 62-64 gb come out the error "Your System Has Run Out of Application Memory".

This project that you see below have like 559 items (video and audio) with many cut, every clips duration is like 1-3 sec. If I try to export that most of the time the export fail. If I put the same amount of clips on timeline but without doing any cut the memory refresh every 2-3 min and don't even reach 25 gb

The problem can be solved by doing the optimized option on part of the used clip, but that is waste of time and when you have a project like that if you optimise every clip your library reach 1,8 TB.

I had the same issue with the Mac mini 16gb, I bought the Mac max hoping that solve the problem.... You have no idea how I feel now....

Btw sorry for my English

Valo

Hi Valo, I found a workaround actually I wanted to create a video about it, but no time. Here’s what to do:

While FCP is exporting you need to observe the process “VTDecoderXPCService” once it reaches a critical size, in my case around 30Gb of memory then you need to go to your PROJECT Icon in final cut. Right Mouse click and select ä “Dublicate Project” (I am not in front of a mac at the moment) and WAIT for c.10-15 Seconds. Opening the new window will reset VTDecoderXPCService and it will start again at zero. it is important to keep the new window OPEN until it reset the project (the new window is the one where you can change the project Settings with the resolution and frame rate and what not)

It works on all my macs, regardless of the Operating system. Sorry that I didn’t share it earlier, let me know if you need a more detailed description happy to help it is such an annoying thing and I am still boiling, but at least you can finalise your project and make your customers happy!!!

Hi Wil!

Thank you so much for your reply.

Meanwhile I was looking on an other forum and I found an other solution that someone also posted here in the previous post but he said that don't work on Monterey, probably he missed a detail.

Meanwhile you export and “VTDecoderXPCService” reach the critical size "for me is 120 gb" you just need to go on the browser of final cut and play a clip that is longer than 15 sec. you can't just play the timeline, because probably you don't have a clip so long. Also an audio file work

In that way the memory also refresh!

If you haven't already done so, please report the problem and your workaround to Apple so hopefully they can have a look and work on a fix.

Final Cut Pro->Provide Final Cut Pro Feedback...  or use this link Feedback - Final Cut Pro - Apple

done, by the way as Valo, I tried the play the clip workaround and it works, I read it before in this threat, but I played the TIMELINE which didn’t work @all: YOU NEED TO PLAY A 15SEC CLIP WHILE EXPORTING, A CLIP WHICH IS IN ONE OF YOUR EVENTS. At least that worked for me as well, but opening the duplicate project window works as well. Anyway Valo many thanks

Hi Tom which Camera did you use? I am using the sony a7s3 and A1, I created an artificial project and took it to an apple shop on my external SSD, on all computers the same, non was able to export the project. I essentially did the same like you + Standard transition “dissolve”, added two music audio files and stabilised all the footage, film length 30min.

What won’t work? There are multiple work arounds, all basically making the application do something else when it gets into memory pressure. It’sa major bug for a group of users with specific media settings.

Hi, I just tried to upgrade at Ventura and Final cut 10.6.5 on my mac mini and they seem fixed something.

The finder alert pop-up keep come up, but after few minutes it refresh the memory and the exportation is successful.

I tried it with a fake project, because a won't upgrade my mac studio in the middle of the project.

What is the main workaround you are doing? I have found out that if I can open up QuickTime and screen record during the export then it will export the file without issues. It will take 2-3 hours which is significantly longer and is extremely frustrating. I use a Sony alpha A7 IV. Shoot in 4K XAVC. I also use a Go pro 10.

This fix has been temporary and is very frustrating for such a long export time, but at least has worked for one of my videos so far.

The easiest way: While you are exporting check with the activity monitor your memory consumption, once the process "VTDecoderXPCService Service" gets over 25GB, hit a right mouse click on Your project file (within FCP) and select "Duplicate Project as..." after that a window will open, do nothing and wait around 15 seconds that will reset the VTDecoderXPCService and your export continues, repeat as often as needed while you are exporting

same problem here, Mac studio , canon R5c and gh6 , 4k 50p

I can't believe this hasn't been fixed yet. It's a serious problem and it's clear that fcpx is involved. where do you put the complaint to apple?

I have called them and spoken to them multiple times over the phone. They act like it isn't an issue and keep saying it is because there are issues with my camera files. Meanwhile tons of other people are having this issue as well. It isn't related to the "files". I have used different files for approximately 10 different projects and they have seen the system completely shut down every time. They keep asking me to do other things and nothing has worked aside from these random workarounds posted in this thread. This has been an ongoing issue for me now for 9 months.

I had the same experience with their service, they were constantly saying “it is caused by the camera”, “the files”, “other installed software”, the worst thing is that they are not aware of those awkward workarounds, every time the call ended with, “sorry can’t help”. Extremely annoying, btw the new MacOS causes the same error.

I started writing comments on Youtube on successful FCPX channels, users have the same problem and are thankful if I post the workaround - that is far more impactful than counting on Apple, they don’t care about this bug.

It seems that we are witnessing the slow death of FCPX. Poor updates, bugs... same procedure with Fcp7. I've been working with apple for 20 years and it's always the same. The development teams of the pro apps are disappearing. Davinci Resolve seems like the best way to go right now. A real shame.