Just to confirm that using the “limited resource mode” is working as workaround till this problem is fixed.
I didn’t have to change the code to avoid this method/function.
Sure I can send you the images set you requested (and I will), but remember that I tried to replicate the problem using Ubuntu and even another raspberry pi connected to the same hardware via Indi as a server and I was not able to replicate the problem.
The only way I was able to replicate the problem was through raspberry pi working as dev device doing remote deployment and debugging on the rig itself.
C9.25, HEQ5, Pi 4 Kstars/Indi, MyFocuserPro2, OAG with ASI120MC guide, f/6.3 reducer, ASI533MC Pro
WO Z61, iOptron SmartEQ Pro+, Pi 4 Kstars/Indi, MyFocuserPro2, ZWO OAG with ASI120MM guide, ASI183MM Pro, ZWO EFW (LRGBHaS2O3)
Would you be willing to test out a shot-in-the-dark fix for me?
Obviously, when you test this, disable limited-resources-mode, so that it would normally crash after your 3rd iteration.
You would need to clone my fork of my KStars repo and test with a new branch (called wcs-fix1) from the current HEAD in that codebase:
git clone invent.kde.org/murveit/kstars.git
git checkout wcs-fix1
and then compile that KStars tree I suppose the same way you've set up other compiles, and execute the binary you compile, and run your test.
This has a few small changes to fitsdata.cpp, fitsview.cpp, fitsview.h which you could see by using git difftool.
It it works, of course great and let me know. If not, please send along a log with at least FITS debugging enabled.
I really appreciate your efforts. I'm pretty much out of ideas. However, just in case, I simplified the code, and added a bunch more logging in one more commit.
If you have the patience, please try to git pull again from my wcs-fix1 branch in my fork and send me the logs (assuming it fails).
If you're going to try and chase down the issue, here's one thing you can try. The only change I can think of related to polar alignment in the last several months is this.Jasem moved all the code into its own file. If you want, check out the version of KStars right before Jasem made that change and see if things were better before that change.
In the main KStars tree:
git checkout faa28833
This should put you right before his change, about a month ago. You could try to compile and test that without limited resources mode and see if things were working back then. In general you can use git checkout to go back to arbitrary commits in the codebase.
any updates on this please? will i be safe to upgrade software. at the moment reverted back to stellarmate v1.5.9 where the polar alignment routine works fine. but having just bought a new scope (hence the cloud and rain here now) and adjusting my rig shall i stick with 1.5.9 or how do i enable this limited resource mode workaround. i have v1.5.9 and and 1.6.0 on different sd cards so backups but with said weather here not had chance to test polar alignment routine.
thanks in advance and for all the effort everyone puts in here.