Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6

Started by Tailspin45, February 28, 2024, 06:51:17 PM

Previous topic - Next topic

Sander Berents

All that seems to be Sonoma specific behavior, and document versioning related (Observatory's integrated Time machine support). I wonder if that is the underlying problem, that there is an obscure conflict going on with how Observatory handles versioning and some undocumented changes in Sonoma. I haven't touched that part of the code for years, so it is really a change in Sonoma that causes this.

The Observatory Demo has versioning disabled, but it doesn't allow saving libraries so we cannot test this theory with it.

I'll look into that and also add a few (hidden) settings to Observatory in the next update so that feature can be disabled and we can test if that "solves" it.

What's weird is that I have never seen this behavior myself on Sonoma. I have only been running Sonoma on an Apple silicon machine though, while you run it on an Intel machine. I have now upgraded one of my Intel machines to Sonoma as well, and maybe that allows me to reproduce it.
Sander Berents
Code Obsession, LLC
https://codeobsession.com

Tailspin45

Sounds like a plan. I look forward to the next update.

Tailspin45

Are you actively working on the next update or should I look for another solution (Observatory is useless to me as things stand)?

Sander Berents

I cannot reproduce it. But Observatory 2.0.5 will contain two new settings that may solve the issue for you:

  • The ability to disable library versioning (the Time Machine integration);
  • Explicitly set the number of CPU cores to use for importing.

I am still working on a few other items before releasing it.
Sander Berents
Code Obsession, LLC
https://codeobsession.com