Recent posts

#11

General Discussion / Re: Termination Reason: Nam...

Last post by Sander Berents - March 06, 2024, 08:44:47 PM

Did you recently upgrade to macOS Sonoma? Having two windows open for the exact same library seems to be a macOS Sonoma-only regression. One that I have not been able to reproduce. It shouldn't be possible, but with Sonoma it apparently is. Observatory cannot work correctly in that state. Its library versioning (time machine) is supposed to help you restore an Observatory library to a previous state, but it sounds like it is in a state where that is not even possible.

#12

General Discussion / Re: Termination Reason: Nam...

Last post by Tailspin45 - March 06, 2024, 01:53:57 PM

When you delete that folder, make sure to empty the trash afterwards so Observatory can really not find it.

I did

Did it crash now for a folder with new lights or old ones?

Both

The crash reports contain many kinds of different activities that are happening during importing. I wonder if the crash happens during decompressing XISF images. What version of PixInsight are you using?

I always update when a new release comes out. Currently using 1.8.9 - 2 Build 1601.

I'm trying to load images from 2023, FITS header doesn't include what build was used, but it was version  1.8.9 - 2

Can you check if this is happening with other image formats?

Yes, it is.

What about older XISF images?

2024 images were imported without an issue. I'm trying to load older albums (session). All loaded ok until November. I have a vague sense that the issue is large folder imports. I've been able to load individual files and managed to load on folder with 59 images. But a folder with, say, 200+ lights will always hang or crash

Did you select a different compression method for XISF files?

No.

---

I continue to get an error msg: This document could not be autosaved. The file doesn't exist.

But it does. And if I use CMD-S it saves fine. And I can launch by double-clicking on 2023.observatory.

However now two windows open, both named 2023.observatory. That didn't happen earlier today.
Just restarted from the crash log "Continue" and have just one library open.

Back to my question from several messages ago: do you have a tool that will rebuilt

BW, often, but not always, after a crash I have to force quit Finder, whatever that proves.

Just tried to create a new library with 2022 data, and it won't import anything using menu or drag and drop. Activity says it  Imported 0 images in 0.1 seconds. Then tried a download from the Virtual Observatory and got this error:
"The document "2022.observatory" could not be autosaved. The file has been changed by another application."

#13

General Discussion / Re: Termination Reason: Nam...

Last post by Sander Berents - March 05, 2024, 09:03:52 PM

When you delete that folder, make sure to empty the trash afterwards so Observatory can really not find it.

Did it crash now for a folder with new lights or old ones? The crash reports contain many kinds of different activities that are happening during importing. I wonder if the crash happens during decompressing XISF images. What version of PixInsight are you using? Can you check if this is happening with other image formats? What about older XISF images? Did you select a different compression method for XISF files?

#14

General Discussion / Re: Termination Reason: Nam...

Last post by Tailspin45 - March 05, 2024, 09:48:11 AM

I deleted  ~/Library/Containers/com.codeobsession.Observatory and tried to load a folder of Lights.

Still crashes

#15

General Discussion / Re: Termination Reason: Nam...

Last post by Sander Berents - March 04, 2024, 11:10:06 PM

Thanks, I have now indeed received automatic crash reports that are related to importing. Probably from your machine.

Observatory is sandboxed, so the App Support and plist files you are looking for are in ~/Library/Containers/com.codeobsession.Observatory. Just deleting the application from /Applications and redownloading it does not remove the settings. Finder nowadays shows that as ~/Library/Containers/Observatory, not ~/Library/Containers/com.codeobsession.Observatory as before  .

#16

General Discussion / Re: Termination Reason: Nam...

Last post by Tailspin45 - February 29, 2024, 12:38:37 PM

New wrinkle: Tried to close 2023 and then open 2024, but Observatory said 2023 couldn't be found, did I want to create a duplicate. I said yes and now is not responding.

Force Quit, Reopen. Now there are two albums for every session, M31 subs in NGC 7000 albums, etc. Most dupes contain no images

Timemachine wouldn't restore the 2023 databse  (locked files?). By chance do you have a tool that will rebuild the database/index?

#17

General Discussion / Re: Termination Reason: Nam...

Last post by Tailspin45 - February 29, 2024, 10:02:12 AM

Deleted app, downloaded new copy from App Store. Problem persists.

Couldn't find any App Support or plist files or I would have deleted them too

#18

General Discussion / Re: Termination Reason: Nam...

Last post by Tailspin45 - February 29, 2024, 09:19:28 AM

Share with app developers was off. Crash report attached.

Tried loading just one session, any session. No joy.

Restart didn't help.

Disk Utility ran successfully on the volume where I save previous year's data. Observatory is on internal SSD

#19

General Discussion / Re: Termination Reason: Nam...

Last post by Tailspin45 - February 29, 2024, 09:13:32 AM

Is there an Observatory 1 / Observatory 2 switch somewhere other than Settings?

IOW, it seems you're saying Obs2 can run as if it were Obs1.

If that is correct, how are the modes selected?

#20

General Discussion / Re: Termination Reason: Nam...

Last post by Sander Berents - February 28, 2024, 10:01:17 PM

I haven't received a full crash report from Apple yet. The only ones I received are for the Quick Look plugin (may be related to the colorful icon issue you have been having). Unless you have disabled the crash report sharing in your Analytics & Improvements System Settings, I should receive it in a few days, which should help me find the underlying cause of the crash.

It sounds like it could be caused by a single November or December image though. It may not be consistent because Observatory 2 imports multiple images simultaneously^*.

^* Unless it runs in Observatory 1 mode, in which case it imports images sequentially (one CPU core only), which is way slower.