Using the nightlies Build: 2022-03-10T15:37:41Z on an Odroid Release 20.04.4 LTS (Focal Fossa) 64-bit Kernel Linux 4.9.277-122 aarch64
During a test of the Scheduler it appears that StellarSolver crashes during the beginning of guiding.
#7 0x0000007fb697574c in StellarSolver::~StellarSolver() (this=0x7f587c4100, __in_chrg=<optimized out> at /media/odroid/T5_1T_SSD/Projects/stellarsolver/stellarsolver/stellarsolver.cpp:45
Can you update your stellarsolver? I just recently added the ability to delete a stellarsolver without danger of it crashing when deleted due to running threads, but you might not have that version of StellarSovler. I just released a 2.1 version. Please try that. KStars now deletes the stellarsolver when doing Star Extraction.
So I'm still having problems with KStars crashing from a Stellar Solver pointer? during guiding, I think. This is with an updated StellarSolver installed after Rob suggestion, via the Software Updater on Ubuntu 20.0.4, and another git pull of the libraries and kstars
echo ================================================================
echo Part 2: Update the repositories
echo ================================================================
cd $p/Projects/indi
echo $p/Projects/indi
git pull origin
echo ================================================================
cd $p/Projects/indi-3rdparty
echo $p/Projects/indi-3rdparty
git pull origin
echo ================================================================
cd $p/Projects/kstars
echo $p/Projects/kstars
git pull origin
fi
# Clone and install Stellarsolver
if [ $run_stellarsolver ]; then
echo ================================================================
echo ================================================================
echo Part 3: Stellarsolver
echo ================================================================
mkdir -p $p/Projects;
cd $p/Projects
rm -R ./stellarsolver/
git clone https://github.com/rlancaste/stellarsolver.git
./stellarsolver/linux-scripts/installStellarSolverLibrary.sh
echo Stellarsolver has been installed
fi
Not quite sure what is different in my situation versus the developers' environments.
Ok, we could change it back in kstars to the way it was before, using just QPointer instead of std::uniqueptr. That would allow it to stick around a little longer and not get deleted while it is still running threads.
With a compile about 1/2 hour ago, during a scheduler test using the simulators, it survived all steps of starting up (track, focus,align, guide setup), but after the 1st downloaded image, it crashed, so perhaps you've found the culprit in the std:uniqueptr, but of course this is conjecture.
Perhaps coincident with Jasem's various memory leaks update invent.kde.org/education/kstars/-/commit...516ed40b3445bf43dbdd
my KStars Build: 2022-03-12T13:23:17Z 3.5.8 Beta on Ubuntu Release 20.04.4 LTS (Focal Fossa) 64-bit Kernel Linux 4.9.277-122 aarch64
Bleeding Edge build (the subject of this error report) appears to be running well now.
Only tested via running a scheduler job using the simulators.
Yes, I had written a merge request for kstars yesterday, but in the middle of Jasem's commit that you mentioned, he did pretty much the same thing my merge request would have done. So yes, that should be fixed I hope.