![]() ...
·
![]()
·
1
like
|
---|
Hi no issue here on my MBP 13 Sonoma last version 64Mo ram.
|
![]() ...
·
![]()
·
4
likes
|
---|
Okay so here is something interesting I found out that seemed to fix the crashes for me: The main problem causing all this mess seems to be related to ImageSolver or the Astrometric Solution of a file in general. If you have an image that will crash PixInsight 100% when using a process (I tested with StarXTerminator), try this: Use ImageSolver (with Distortion Correction unchecked, otherwise this script will crash) to get a valid Astrometric Solution. This should prevent further crashes. So for me, once a file had a valid solution, PixInsight would never crash during editing the specific image anymore. I hope this helps for all the people experiencing problems as well. Johannes Edit: Nvm, now this doesn't work anymore. |
![]() ...
·
![]()
·
1
like
|
---|
It keeps crashing during WBPP. M1Max 32 GB with latest macOS. Had to roll back to 1.8.x
|
![]() ...
·
![]()
·
1
like
|
---|
juan claims to have fixed the problem and so hopefully with the next release we will be ok.
|
![]() ...
·
![]()
·
1
like
|
---|
Haven’t upgraded to Lockhart yet for me…Mac OS on Apple chip…going to give it some time for bugs to get sorted
|
![]() ...
·
![]()
·
1
like
|
---|
Johannes Maximilian Möslein: Same issue here on iMac M3. Also all external processes as RC BlureXT, GraXpert etc while shown in repository not offered in Process list. Went back on 1.8.9 and all fine again. Does anyone know where to find/hoe to activate external tools in 1.9.1? |
![]() ...
·
![]()
·
1
like
|
---|
Even the latest Mac version before 1.9 was iffy for me. Any time I had it open for 10 minutes +, I would get segfault errors galore and they always lead to the app crashing some minutes later. The segfaults seem harmless, as they say on the forum, but it's broken. 1.9.1 still crashes on me, but this time it goes straight to the desktop without any error. M3 pro as well. Nothing seems to get around the segfaults still, which makes me wonder if it's just the same issue but it's C.T.D. anyway. |
![]() ...
·
![]()
·
3
likes
|
---|
There seems to be an issue that PI 1.9.x crashes during WBPP, usually when calling the StarAlign, the FastIntegration or the ImageSolver routine. This seems to be related to the distortion correction (switching it off usually results in stable runs), and its occurrence seem to be fairly random but more frequent for large number of files - probably some sort of memory/addressing issue [?!]. Judging from the pixinsight forum, the developers have tracked down the problem and found a solution, and plan to apply it with the next release. Matthias |
![]() ...
·
![]() |
---|
Even the latest Mac version before 1.9 was iffy for me. Any time I had it open for 10 minutes +, I would get segfault errors galore and they always lead to the app crashing some minutes later. The segfaults seem harmless, as they say on the forum, but it's broken. 1.9.1 still crashes on me, but this time it goes straight to the desktop without any error. M3 pro as well. True, i forgot about that. I got segmentation violation errors when moving the mouse, dragging icons or using processes via the triangle drag. |
![]() ...
·
![]()
·
1
like
|
---|
Thx for the status, community. Will wait for a stable version. |
![]() ...
·
![]()
·
1
like
|
---|
I had serious issues on 1.9 earlier in the week, but I just installed 1.9.2 build from yesterday and I can finally run WBPP without crashing to the desktop. I've processed 3 jobs so far and no console errors either. Small sample size here but it's okay now on my M3 Pro. You don't have to worry about your license file if you are downgrading or upgrading installations either, so it's quick for me to change back if it goes berserk again.
|
![]() ...
·
![]()
·
2
likes
|
---|
1.9.2 seems to be working on my Mac now. No crashes after working on 4 data sets. Hope they got it.
|
![]() ...
·
![]()
·
1
like
|
---|
1.9.2 seems to be more stable on MacOS.
|
![]() ...
·
![]() |
---|
PI 1.9.2 I’ve run the WBPP 1 time with 519 light frames with 2x drizzle, separate channels (OSC) and no crash, but the RC astro tools and GHS are still not working. |
![]() ...
·
![]() |
---|
All the RC tools are working for me.
|
![]() ...
·
![]() |
---|
Mel Martin: They worked fine to begin with, but the BXT crashed PI and they all stopped working. I’ll re install 1.9.2 tomorrow |
![]() ...
·
![]() |
---|
1.9.2 is now installed and working even better than 1.9.1 for me. So far it seems much more stable.
|
![]() ...
·
![]() |
---|
Hi Gary, are you using external processes / scripts as well? If so: also working stable? Any issues to activate etc?
|
![]() ...
·
![]()
·
1
like
|
---|
1.9.2 has resolved most but not all of the problems on my Intel MBP. ImageSolve only works with Distortion Correction disabled. There are multiple strange screen effects going on within the desktop, generally menus not working as expected or icons not responding. Right clicking on an image always produces the Workspace menu seen when clicking on the icon in the top right corner of an image frame. I am back with Ripley as Lockhart seems to offer little of benefit to NB imagers in my opinion; the MGC process is some way off being useful. I have a bad feeling my 2019 Intel based MBP is well down the obsolete/'no longer supported' list and will soon drop off the end - a bit like me really ![]() |
![]() ...
·
![]()
·
1
like
|
---|
I have a 2019 MBP as well. I was able to run WBPP on 1.9.2 with a data set that has earlier failed on previous 1.9.x versions (114 subframes). But only using combined channels (OSC data). Normally I keep the channels separated. The plate solve still fails if I use my stored Gaia files. Going online fixed also the plate solving. I have 16 GB RAM on my Mac and have a feeling that this otherwise excellent laptop has reached the end of its life as my PI machine. Of course 1.8.9 still works without any issues.
|
![]() ...
·
![]() |
---|
I had multiple issues also with 1.9 and friends here local with 1.91 failing. Concerned about the errors fixed. Mac Studio w/ M2 Ultra here. I was thinking of booting up on a fast SSD so if it fails I just erase the SSD and 1.8.9-3 is still on my main system.
|
![]() ...
·
![]() |
---|
Mac Studio M1Max, 32GB RAM. Since 1.9.2 everything works, except registration in WBPP, it usually drops ca 3% of frames on datasets, that I have processed earlier, without any issues. I usually run it with separated channels for OSC data. it seems to some I/O issue on the disk, but it is the same on both external SSD, on which I usually process as well as on the internal SSD. [2024-12-31 08:02:14] ===== ImageCalibration: 92 succeeded, 0 failed, 0 skipped =====[2024-12-31 08:02:14] 0 cached, 92 generated, 0 failed.[2024-12-31 08:07:19] ===== Debayer: 92 succeeded, 0 failed, 0 skipped =====[2024-12-31 08:21:33] ===== SubframeSelector: 276 succeeded, 0 failed, 0 skipped =====[2024-12-31 08:21:48] SS nFailed : 0[2024-12-31 08:39:30] ===== StarAlignment: 91 succeeded, 1 failed, 0 skipped =====[2024-12-31 08:39:30] Registered frame 1: /Volumes/Ricsi_T7_2/Astro/PI/Orion/Panel_2/debayered/Light_BIN-1_6248x4176_EXPOSURE-300.00s_FILTER-L-Pro_CFA/2024-12-25_20-24-15_L-Pro_-20.00_300.00s_0001_c_d_R.xisf —> [ FAILED: Empty output file name ][2024-12-31 08:57:28] ===== StarAlignment: 92 succeeded, 0 failed, 0 skipped =====[2024-12-31 09:15:18] ===== StarAlignment: 92 succeeded, 0 failed, 0 skipped =====[2024-12-31 09:17:33] ===== LocalNormalization: 20 succeeded, 0 failed, 0 skipped =====[2024-12-31 09:20:39] ===== LocalNormalization: 20 succeeded, 0 failed, 0 skipped ===== |
![]() ...
·
![]() |
---|
Has happened to me as well. Lost a lot of time (I have an M2 Mac). I downgraded to 1.8.x same here with M1 Pro |
![]() ...
·
![]() |
---|
Johannes Maximilian Möslein: why didn't you install 1.9.2? that is the version that seems to fix a lot of problems on osx (but people are still having problems with ImageSolver on macs with 16GB of memory) [i might have responded to an old message written before 1.9.2 came out, astrobin might have fooled me] |
![]() ...
·
![]()
·
2
likes
|
---|
Finished processing an image on 1.9.2 on MacOS (MacPro 2019, 16 core Intel Xeon, 160GB RAM). No crashes and all the tools worked as they were supposed to. Also processed 320 files through WBPP without any issues. What did come back though is the occasional slurry of red text in the process console and erratically moving views and icons. I believe this issue had something to do with the QT version used. I don't think this is related to 1.9.2 and so far it did not crash the application, but annoying nevertheless. |