I’m guessing that it is trying to load the last saved gig file, and there’s an issue with a plugin in one (or more) of the rackspaces.
Try holding down the Shift key while loading GP until you get the Temporary Startup Options screen, then de-select Load last gig file and press OK. This will load a new, blank gig.
You can try to load the corrupt GigFile and you’ll probably be able to see which Rackspace GigPerfomer closes when it loads.
Then you can load the gigfile (a copy…) with a text editor, delete this one rackspace, save the file and load. If only this rackspace is corrupted, it should work.
Can you trace what happened so the problem arised? Driver update, plugin update, OS update, …
If your gig file worked well and now it doesn’t I suspect it is a plugin issue.
The Temporary Startup Options has a logging feature. If Gig Performer starts loading plugins and then unexpectedly quits, that log will show what is the last plugin that GP tried to load.
So, disable that plugin and try to load GP. If it works, you’ve found yourself the culprit.
Because most DAWs don’t use as much of the functionality of the plugin API as GP does and so if GP uses functionality that wasn’t tested by the plugin developer, it can be broken.
VM Region Info: 0x8 is not in any region. Bytes before following region: 4380684280
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
__TEXT 1051bf000-108f4b000 [ 61.5M] r-x/r-x SM=COW /Applications/GigPerformer5.app/Contents/MacOS/GigPerformer5
Plugin developers rarely write and test plugins for live applications, and as a result they can sometimes shortcut in certain areas of the technical specifications because those areas don’t tend to appear in most DAW’s. However, GP will often expose those areas because it is utilizing more of the plugin specifications.