Maximum Still image/Crashes?

Hi all, wondering if there is a maximum image size that is acceptable for FCPX?  Having some odd crashes and wondering if this may be the problem? - Thanks

The maximum image size is governed by the number of images and the graphics capabilities of the system, what GPU and how much VRAM.

Hi Tom - I'm on a 2018 MBP with an intel UHD 630 with VRAM of 1536 mb and Radeon Pro 560X with 4GB of VRAM - Thanks

If there are only a few large images in a project than the image size probably is not a factor in the crashes. That's a guess without knowing what a large image is for you. If you have Chrome installed you should uninstall it completely.

Hi Tom - don't have chrome didn't know there was a problem with it? I'm producing 8 x 3 min videos with a m ix of stills up to 7000 x7000 and live action - thanks Bob

I use full frame Nikon z7 images all the time without problems. 45 mB images, 8k + on the long side

paz wrote: Hi Tom - don't have chrome didn't know there was a problem with it? I'm producing 8 x 3 min videos with a m ix of stills up to 7000 x7000 and live action - thanks Bob

When FCP crashes it should raise a dialog showing the stack traces of each thread. While that's on the screen do a CMD+A to select all, CMD+C to copy, the paste that to a TextEdit document. Zip that file and upload it to me at this location and I'll examine it:  www.transferbigfiles.com/dropbox/joema

Cheers Dave thanks for this good to know appreciate your info

Thanks very much for the offer the next time it happens I'll Wendover to send the crash report - stay safe 

paz wrote: Thanks very much for the offer the next time it happens I'll Wendover to send the crash report - stay safe 

OK I received the crash dump. Here are some comments:

- MacBook Pro 15,1, 6-core i7, 32GB RAM, Radeon Pro 560X, 4GB

- FCPX 10.4.10 on Catalina 10.15.7

- It crashed in thread 81 when doing a Metal call then entering GPU code. 

Other items within FCP memory at time of crash:

- Crumplepop VideoDenoise 

- Many different effects from Pixel Film Studios

- VTwinFX from CoreMelt

- MotionVFX plugins

- FxFactory plugins

Any plugin using the FxPlug 3 framework (several of the above) runs within the address space of FCP. Any thread from any plugin can crash or destabilize FCP. This will hopefully be addressed in the future as plugin developers move to FxPlug 4.

Some plugin code can remain in FCP memory even after a fresh launch if you don't open a timeline with those effects. However I'd first recommend you make a snapshot copy of your timeline, select all clips with Edit>Remove Effects and see if it still crashes.

There have been many problems traced to Pixel Film Studio plugins. If possible try removing those or make a test library and copy a project over there, then remove those from that test timeline. Here is how to remove those plugins:  store.pixelfilmstudios.com/how-to-uninstall-a-plugin/

An intermittent or random problem is difficult. I'd also suggest you update all CoreMelt plugins using their installers:  coremelt.com/pages/downloads

CoreMelt is a good company but if the plugins are old it may cause problems. If you are not actively using those, consider removing them with this utility:  support.coremelt.com/hc/en-gb/articles/2...ove-CoreMelt-plugins

Thank you so much for having look at the crash report ad highlighting all teethings that might have been the problem - It would be great if FCPX allowed plugin to be disabled at the flick of a switch?? - Cheers stay safe )