I enqueued several jobs. When I abort a currently running job, it will be aborted but also the next job in line is started immediately. I abort this too... this game goes until the end of queue (unless I postpone all other jobs prior to aborting the running one).
Oh, and pressing "Stop" prior to "Abort" (on main GUI or worker) has no effect.
Using build 2237. Problem did not occur in previous versions. Aborting a job there actually aborted the job and did NOT start the next one.
Last ~50 lines in attached log file show the cases, when the next job starts in the same second, when another job got aborted.