When exporting, we randomly get the following error:

"Exception: std::exception, what:"Segmentation fault" in thread "Adopted Thread", at address    0x0"

We then have to quit MC6.0.1 and restart in order to get the export to work.

Any ideas or help is greatly appreciated.

We're getting a very similar problem. Did you ever resolve this?

We're on MC6.03/OSX 10.7.4/ Unity MN Client 5.5.1, and MC6.01/OSX 10.7.2/ Unity MN client 5.5.1. 

On export from Bin-level to H264 1280x720 from a 1080/23.98 project, we get a similar pattern of failure:

1. The first is a general, " Exception: std::exception, what: "Segmentation fault" in thread "Adopted Thread", at address     0x0"

2. On 2nd attempt, pops " errcode: Exception: Movie export from procedures FAILED!, errcod: 4294967247"

Sometimes requires restart of system, sometimes just application to continue.

Export to local or Unity workspace fails with equal frequency.

Thanks!

I have found this is ushually due to a corrupt effect render. The problem is to try and figure out where it is. Try exporting sections of your timeline "same as source" as it's quicker and should allow you to find the cuprit without wasting days. 6.03 behaves much better than 6.01 for exports.

Clearing bin memory helped me most of the times.

Restarting typically fixes it for me.  It's the only workaround I know of at this time.

Any new info on the segmentation thing

What version are you running Dingo?  You have to get to 6.0.3 at a bare minimum.

Hi all,

Greetings from the Great Land Down Under.

This error is still driving me crazy.  It has gotten to the stage where I am almost too scared to use the Media Tool any more!  This error was allegedly "fixed" in v5.5.3!  This is clearly not the case.  I sometimes get it when editing but nearly always when using the Media Tool (which I dearly love by the way).

It would be just awesome to get this error finally put to rest once and for all or I'm just going to have to jump ship and migrate to Windows!

Dave Forsyth

We have about 20 Mac Pros here running 6.0.3 and we still get the issue on multiple computers.

Same here - exports tow or three times then will get some kind of segmentation error. Running 6.5. Been a problem since 5.x I think. Can Avid jump on this one ? In addition I still dont understadn why the "fast start" flag isnt preserved on exports, I constantly have to re-save any export from Quicktime in order to have the "fast start" flag work for postings. This has been an issue since versio 4 I think!

If any of you have export issues using a default export template, please try altering one setting, thus making it a custom setting, and seeing if there's any improvement.

Excellent thought Todd....I have found some combination of;

altering export setting,

leaving and returning to the app,

rebooting,

tossing the settings file

turning around three times......

Seems to work....weird.  Be great if this was fixed.  Still on 6.0.3 cause I hear it ain't better in 6.5....true?

Still not fixed in 6.5 as I'm having the same problem.  Usually makes me have to force quit and start over with another setting.  I've tried exporting to desktop, network, Terrablock.  I've deleted the setting and created a new one (usually it's a setting for a 480x270 H.264 file).  I've tried transcoding the sequence to make sure it's all the same format.  Once I get the error it won't let me export anything and I have to force quit the Avid and try again.  Resorted to exporting uncompressed file to desktop and using Adobe Media Encoder to make the file.  Extremely frustrating.  

Mac Pro 2x3GHz Quad Core Xeon, 12GB RAM, OSX 10.8.2, DeckLink HD Extreme 3D+, GeForce 8800GT, TerraBlock storage.

No help really but this seems to be an enduring Mac issue with MC. Segmentation faults seem to be a regular issue on the Mac platform. I wonder what it is in the code or error handling that makes it an isue on the Mac but not the PCs?

No help here either but I thought I'd add my voice to the chorus of increasingly frustrated (dare I say "dissatisfied"?) Avid users on the Mac platform who have had it up to here (visual: hand placed horizontally under chin) with this stupid "Segmentation Fault" error.

For those users on Mac not encountering this error, good luck to you.  I hope it never happens to you.

But for those of us who do get it, the inexplicable, apparently random nature of this error is driving us bananas!!

It has honestly got to the point where I am just too scared to use the Media Tool any more because I know that while it is opening I am going to get this error and have to quit and relaunch.  

It would be somewhat comforting to know that someone at least is looking into this increasingly widespread problem and trying to fix it.  I never had it before v3.0 so in the big v3 rewrite, I think someone broke something.

Please don't make me migrate across to Windows becasue as soon as I do, the corporate IT police are going to swoop down and cripple my Avid system with all kinds of devilish permissions, security policies and God-only-knows what other vile Novell netowrking and administtrative restrictions they devise to make a perfectly good HP workstation feel like you're wading through treacle!

Kill the Segmentation Fault!!... please.

Dave Forsyth