Alfred,
I see from your video that the solver's computations were not aborted after the timeout, but I cannot reproduce that on my Ubuntu 22.04 system -- that is, the plate-solve threads are properly terminated after timeout for me.
I think it is likely that this has something to do with how Qt kills threads in your environment, and am not sure what to say about it. Luckily, at least for image overlays, it is not an ongoing thing (that is, mostly you plate solve one day, and then use the information in the weeks/months ahead). If you want to investigate further, as I see from the other thread you can compile and run kstars, you can do as follows:
1) make sure kstars is sending stellarsolver the abort command:
Perhaps before line 199 add
fprintf(stderr, "Calling abort\n");
invent.kde.org/education/kstars/-/blob/m...solverutils.cpp#L199
and before or after line 55 add:
if (m_StellarSolver.get()) {
fprintf(stderr, "sending stellarSolver the abort message\n");
else
fprintf(stderr, "StellarSolver doesn't exist so can't abort it.\n");
invent.kde.org/education/kstars/-/blob/m.../solverutils.cpp#L55
then you'd run KStars from the command line, and look at that terminal when the timeout happens and check to see if you're getting those printouts.
2) If you wanted to go further into stellarsolver, you'd need to compile stellarsolver and install the compiled stellarsolver, perhaps making these changes:
At the start of StellarSolver::abort() add a printout:
fprintf(stderr, "aborting stellarsolver\n");
github.com/rlancaste/stellarsolver/blob/...ellarsolver.cpp#L638
and at the start and end of the function abortandwait() add
fprintf(stderr, "starting abortandwait()\n");
fprint(stderr, "abortandwait is done\n");
github.com/rlancaste/stellarsolver/blob/...ellarsolver.cpp#L647
Perhaps those things can give us some clues.
Hy