-
FCP Crashes: EXC_BAD_ACCESS (SIGBUS) Please Help!
Hi,
I have to finish a big work for tomorrow, and when I try to export (1920×1080 proress with diferrent types media on the sequence. Exported as a non-selfcontained movie) FCP will crash showing this message: EXC_BAD_ACCESS (SIGBUS).
I have tried exporting as a selfcontained movie and doesnt work either.Daniel Sepulveda
Cámara Televisón
Bogota-Colombia -
2 Replies
-
On the 2 occasions I can recall running into the same issue, the first was related to the MAC user being created after the guilty footage was ingested and after an OS update.
The 2nd time we narrowed it down to having .motn files in the timeline as opposed to rendering our motion work out to .mov and inserting it.
Does your export always crash in the same spot? If so, you may be able to estimate where on the timeline any offending files may be.
-
Hello everyone, not too much activity in this thread for awhile but I recently went through the same problem so I figured I would share my insight. My issues started after we got out i7 imac back from Apple (for a logic board swap) with a fresh install of 10.6. I installed FCS 3 and all of our plugins. We’ve got 2 other machines running FCS 3 with no issues. What happened to me was i would go to open up one particular project on the i7 and FCP would crash about 40% into loading the project. BUT the project opened fine with on the other machines with the same plugins installed and everything. Some other threads recommended Digital Rebellion’s Pro Maintenance Tools (https://www.digitalrebellion.com/blog/posts/pro_maintenance_tools_2.0.5_and_pro_admin_1.5.3_released.html)
I downloaded it (15 day free trial) and opened the “plugin manager” feature. This is a pane that allows you to disable all or one of your plugins manually without uninstalling or trashing them. Basically what I did was systematically disable each 3d party plugin and try opening the FCP file until I came across the culprit. It was Boris FX’s “Contunuum Express” like i said, all of our plugins work beautifully on our other machines, but if I disabled it on the i7 it solved my issue. It was likely a glitch in the install of the plugin.
I understand that many things can cause a SIGBUS crash, and reinstalling the OS and/or FCS will likely solve the issue, but consider checking into this before you spend 1/2 a day reinstalling all of your software.
Cheers,
Ethan Gallo
Ethan Gallo-
Reply to this Discussion! Login or Sign Up