https://bugs.kde.org/show_bug.cgi?id=378158
Boudewijn Rempt <b...@valdyas.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
|ta/2071a0701c68caa92eb81150 |ta/3a793d0208c8b88211764be2
|77f8379b3803041e |5b0a942d25a192fa
--- Comment #2 from Boudewijn Rempt <b...@valdyas.org> ---
Git commit 3a793d0208c8b88211764be25b0a942d25a192fa by Boudewijn Rempt, on
behalf of Dmitry Kazakov.
Committed on 06/04/2017 at 10:02.
Pushed by rempt into branch 'krita/3.1'.
Fix a race condition in KisUpdateScheduler
If spareThreadAppeared() signal comes between `m_d->processingBlocked = true`
and `m_d->processingBlocked = false` lines, then no update will be started
even when we return from the barrier lock call.
In normal case, when the barrier lock is successful, processQueues()
is called in the unlock call, but here it doesn't happen.
M +3 -1 libs/image/kis_update_scheduler.cpp
https://commits.kde.org/krita/3a793d0208c8b88211764be25b0a942d25a192fa
--
You are receiving this mail because:
You are watching all bug changes.
