https://bugs.kde.org/show_bug.cgi?id=397970
--- Comment #1 from TallFurryMan <eric.dejouha...@gmail.com> --- Two possible extensions to this issue from @wreissenberger: "The setup is the following: create a schedule with two jobs for the same target with the same sequence job (say 1xLum for example). The first job starts and captures the first frame. And here is where the problem occurs: now calling Scheduler::updateCompletedJobsCount() detects the one frame, but when evaluating the second job (which did not run yet), the value in the captured frames map is overwritten. This leads to an endless loop of the first job." "I observed that the counting update happens only after a single sequence is finished and not after each capture." -- You are receiving this mail because: You are watching all bug changes.
