Latest post Sat, Dec 4 2010 2:59 AM by Derwood. 6 replies.
Page 1 of 1 (7 items)
Sort Posts: Previous Next
  • Tue, Oct 12 2010 3:42 AM

    • TrainerDave
    • Not Ranked
    • Joined on Tue, Aug 5 2008
    • Sydney Australia
    • Posts 183
    • Points 2,350
    • Avid Certified Instructors - Video

    "Segmentation fault" in thread "MainThread", at address 0x0

    Getting this error a lot at the school where I am currently working.  Hopefully in the next few days I will have the opportunity to try some things out but it occurred to me that there might be a very simple answer. Idea  I have seen this error only once before outside the school and that is on my MacBook Pro which, apart from running Media Composer v5.0.3, is also running Final Cut Studio... (there, I said it) <gasp!>

    Could it be that this weirdness is somehow linked to both these applications residing on the same partition? (no they are NOT running simultaneously)

    As it is, I am going to try trashing some media databases, try new users etc but I wonder if those who have also encountered this error also have FCS and Media Composer on the same partition?

    Watch this space...

    Home: Dell T3500 Win 7 Pro, MC7 with Symphony option Work: HP z820 workstation, 16Gb RAM Media Composer v7 with Symphony option) [view my complete system specs]
  • Tue, Nov 30 2010 6:02 AM In reply to

    • TrainerDave
    • Not Ranked
    • Joined on Tue, Aug 5 2008
    • Sydney Australia
    • Posts 183
    • Points 2,350
    • Avid Certified Instructors - Video

    Re: "Segmentation fault" in thread "MainThread", at address 0x0

    Hmmm not related to FCP and Media Composer residing on the same partition.  Still getting this error even after a clean install of 5.0.3.  There has to be a fix for this as it is causing students to shy away from using Media Composer in favour of FCP!

    Help!

     

    Home: Dell T3500 Win 7 Pro, MC7 with Symphony option Work: HP z820 workstation, 16Gb RAM Media Composer v7 with Symphony option) [view my complete system specs]
  • Tue, Nov 30 2010 11:07 AM In reply to

    • mjolnarn
    • Top 10 Contributor
    • Joined on Wed, Feb 8 2006
    • Sweden
    • Posts 13,346
    • Points 159,365

    Re: "Segmentation fault" in thread "MainThread", at address 0x0

    What OS ?

    Mac: 17" Macbook Pro i7 2,66 ghz with 8Gb Ram, 500gb 7200rpm drive___ PC_NEW Win10 Pro Mbo Asus Rampage IV Black CPU Ivy Bridge-E 4960X ( = 12 x 4... [view my complete system specs]

    Tomas 

     

  • Tue, Nov 30 2010 10:58 PM In reply to

    • TrainerDave
    • Not Ranked
    • Joined on Tue, Aug 5 2008
    • Sydney Australia
    • Posts 183
    • Points 2,350
    • Avid Certified Instructors - Video

    Re: "Segmentation fault" in thread "MainThread", at address 0x0

    iMac 3.06GHz Core 2 Duo, 8Gb RAM, Mac OS 10.6.2

    Home: Dell T3500 Win 7 Pro, MC7 with Symphony option Work: HP z820 workstation, 16Gb RAM Media Composer v7 with Symphony option) [view my complete system specs]
  • Wed, Dec 1 2010 4:24 AM In reply to

    • mjolnarn
    • Top 10 Contributor
    • Joined on Wed, Feb 8 2006
    • Sweden
    • Posts 13,346
    • Points 159,365

    Re: "Segmentation fault" in thread "MainThread", at address 0x0

    Please follow the link below copied and pasted from the " start here " top post of this forum

     

     

    Media Composer Version Matrix.  Each release of software is listed with the supported Mac models, OS, and QT versions.

    Mac: 17" Macbook Pro i7 2,66 ghz with 8Gb Ram, 500gb 7200rpm drive___ PC_NEW Win10 Pro Mbo Asus Rampage IV Black CPU Ivy Bridge-E 4960X ( = 12 x 4... [view my complete system specs]

    Tomas 

     

  • Fri, Dec 3 2010 4:14 AM In reply to

    • Derwood
    • Not Ranked
    • Joined on Fri, Dec 3 2010
    • Toronto
    • Posts 4
    • Points 40

    Re: "Segmentation fault" in thread "MainThread", at address 0x0

    I get the exact same error every time I quit MC.  It seems to have quit normally, but then when you click on the screen to do anything else the error window comes up along with the spinning beachball and I have to force quit in order to finish the quit command.   Everything seems normal upon next launch of MC and no project info was lost.

     

    MC5.0.3 on clean install of OS 10.6.4, QT X (plus QT7 added for QT Pro functions), dongle registration, MacBook Pro 2.5ghz Core 2 Duo (Nvidia GeForce 8600M GT), 2gb ram, Lacie Quadra drive via FW800 as media drive.

    MC5.0.3 on OS10.6.4, QT X (plus QT7pro), MacBook Pro 2.5ghz Core 2 Duo (Nvidia GeForce 8600M GT), 2gb ram, Lacie Quadra via FW800, 2nd partition with FCP6... [view my complete system specs]
  • Sat, Dec 4 2010 2:59 AM In reply to

    • Derwood
    • Not Ranked
    • Joined on Fri, Dec 3 2010
    • Toronto
    • Posts 4
    • Points 40

    Re: "Segmentation fault" in thread "MainThread", at address 0x0

    FYI.  Problem seems fixed now.  I did 3 things altogether but I think it was installing the 5.0.3.5 patch that fixed it.  The other 2 things I did was trash MC State, Site Settings, Site Attributes.  And also I removed/hid everything from what used to be called the Start Up Items, now called Login Items under Accounts. (took me a while to find it)

    Thought I'd mention in case it helps the OP.

    MC5.0.3 on OS10.6.4, QT X (plus QT7pro), MacBook Pro 2.5ghz Core 2 Duo (Nvidia GeForce 8600M GT), 2gb ram, Lacie Quadra via FW800, 2nd partition with FCP6... [view my complete system specs]
Page 1 of 1 (7 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller