Automate tick data 100% CPU usage after aborting

Hello! When running automate on long period (more than 6 months) on tick data with resources pulled at 100% the CPU usage remains maxed out for more than a minute (usually hour or more) when aborting in the mid way.

Would it be possible to kill the optimization threads when optimization is manually interrupted? Maybe something like this once user has pressed the stop button:

optimizerThread.Interrupt();
if(!optimizerThread_.Join(60000)) {
   optimizerThread.Abort();
}