Hello,
So after more thorough testing, as promised, here are my results:
1 - Subframe selector script crashes as often as for build 1448, however errors are now only printed to the console and not in a modal interrupting message box. I have this issue no matter the files I use (even ones that worked fine either with v1.8.5 or v1.8.6).
Sometimes it happens after 3 files have been measured, sometimes after hundreds. Sometimes it is only a single file, sometimes it is a bunch of them in a row or close to each other. I fail to find any pattern other than the more files you add to the list the more probable it will occur.
I am convinced it is not linked to the data, as sometimes a particular file will work sometimes it won't, but if you wish let me know and I'll be happy to provide you my files.
My tests were conducted prior the module update I noticed today. But as I am using the script I believe my tests should still be valid, unless there are any dependencies with the module. Please let me know, and I will re-conduct tests if needed.
2 - About general use it seems crashes happen especially when I use Star mask module several times (on a small image, details attached).
I have a difficult picture with nebulosity that gets picked up and I am doing trial and error with star mask parameters. So I end up generating a lot of new views (I close them as I generate new ones tho).
After sometime it systematically crashes on my setup with the same error I reported in my previous post (after maybe 20 or 30 star masks have been generated).
I notice it crashes when I try to move new star mask window and it doesn't (instead error is printed in console). If I try closing it, each time I try the same error gets printed on the console after about 10 tries PI shuts down non gracefully.
I found a workaround for this! I believe this might help you pinpoint the exact issue, and help others experiencing the issue...
Interestingly, if instead of left click, I right click on the close button it works. The faulty view is closed with no errors and I can resume work without having to restart PI.
3 - For the performance sudden drop, It is still present but I have measured it a bit more precisely. I would say the slow down factor is closer to 25 times rather than 50.
With build 1457 restarting PI is not sufficient as a workaround but a reboot works all the time.
4 - The bug about opening PI and letting it sit in the background leading to a crash has never occurred on build 1457.
I also wanted to share more information about my system/usage of PI:
A - In PI I make use of 3 workspaces and have tens of process icons on each of them.
Upon opening a project with only process icons and no images, each process dialog appears and disappears. Looking like flickering and is slow to open even-though I have it set on workspace 4 containing no process icons.
This might be normal or already happening in v1.8.5, sorry I don't remember. But I didn't want to discard any information that might help you.
B - In my last post I didn't precise that my SSD is an M.2 2TB drive.
It is partioned in two disks, one containing OS, and one PI data, temp folder and pagefile.
Maybe somehow it could have an impact.
C - I also forgot to precise that all my drives have been trimmed, error checked and have windows indexing disabled.
D - PI swap storage folder is not a system temporary folder.
E - My motherboard is an ASUS Z170 PRO GAMING with latest BIOS installed.
Please kindly let me know if I can provide further help.
Looking forward for your response.
Cheers.
