A new thread is spawned each time the process button is hit. However, the threads are not terminated after hitting the cancel button, but only after a final result has been obtained. Currently, we also limit the maximum amount of threads to 10.
We should find a way to terminate threads immediately after the cancel button is pressed, regardless of the current stage of processing, as to avoid creating "zombie" threads. In this case, placing a ceiling on the maximum amount of threads will be less important.
This may require a decent rework of our threading implementation.
A new thread is spawned each time the
processbutton is hit. However, the threads are not terminated after hitting thecancelbutton, but only after a final result has been obtained. Currently, we also limit the maximum amount of threads to 10.We should find a way to terminate threads immediately after the cancel button is pressed, regardless of the current stage of processing, as to avoid creating "zombie" threads. In this case, placing a ceiling on the maximum amount of threads will be less important.
This may require a decent rework of our threading implementation.