Latest upgrade crashes every time
 

I just had an automatic upgrade (4.0 test v162 r196336) and it crashes repeatedly on opening.

I get an OmniGroupCrashCatcher message that reads: NSInternalInconsistencyException: Unable to swap task exception ports (os/kern) invalid argument (code 4,mask=0x0000107e)

This happens every time I try to open an 003 file. If I merely click on the OO4 icon on my dock, it opens OO4 just fine. But if I then try to open an existing file, it crashes. Every time.

Which means I cannot work on any of my outlines. How do I restore the previous version? Clearly, this latest upgrade is flawed.

This same message has been returned to me:

[QUOTE]Unable to swap task exception ports: (os/kern) invalid argument (code 4, mask=0x0000107e)[/QUOTE]

except I got when trying to upgrade from r196372 to r196376. I rolled back to 372, but got the same message when I clicked on "Reopen windows." When I started it again I skipped that step and was presented with a blank file. I [I]then[/I] tried to open a recent file and the message above returned.

I wonder, though, if it's actually the The Omni Group Crash Catcher that's throwing up the message. When I try to quit or force quit that I get the same message, even when .oo4 is not running.

I've gone back to using OO 3 - everything opens fine it.

Sorry about that. This is caused by hyperlinks in the document. The last good build should be [url]http://omnistaging.omnigroup.com/omnioutliner-4/releases/OmniOutliner-4-r196268-Test.dmg[/url]

You can always return to the [URL="http://omnistaging.omnigroup.com/omnioutliner-4/"]omnistaging[/URL] page to download a past build when major regressions are introduced. We're working on memory management issues right now that has been causing this instability.

Thanks Derek. And yes, the earlier build works fine now.

How will we know when this issue is resolved and it's safe to switch to the latest upgrade?

Ideally it would be noted in the release notes but not everything makes it in there. Mostly just trial and error, this crash is high priority though so it shouldn't be long. I'm trying to keep an eye on the builds and pulling bad ones, but any builds later in the evening likely won't be checked till the morning.

This crash has been fixed in r196516.

Yes it has. Thanks!