https://bugs.kde.org/show_bug.cgi?id=496018
Dmitry Kazakov <dimul...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
|hics/krita/-/commit/23882dc |hics/krita/-/commit/706b558
|7a678a591d5af3c944f9f4f6ca1 |625d79f27cb8f774ea408b1540d
|16cd10 |08a719
--- Comment #8 from Dmitry Kazakov <dimul...@gmail.com> ---
Git commit 706b558625d79f27cb8f774ea408b1540d08a719 by Dmitry Kazakov.
Committed on 11/11/2024 at 16:37.
Pushed by dkazakov into branch 'krita/5.2'.
Fix a possible saving lockout due to incorrect ownership of the saving mutex
Steps to reproduce:
1) Start a very long stroke (that would be calculated for 15 more seconds at
least)
2) Press Ctrl+S to initiate saving
3) When asked to wait for the image operation to complete, press "Save without
waiting"
4) When the next waiting dialog appears, press "Cancel" (you should be very
quick)
Before this patch, the document will fall into a locked up state, when no
saving is
possible. It happened because of a 'return' expression after the saving mutex
has
been taken. This patch changes the ownership of this mutex to a unique_lock, so
returns and asserts will no longer cause a complete lockout.
This dialog could have been triggered by the autosave operation. If the used
"accidentially" clicked "Cancel" button, then the document could end up in
a locked up state as well.
M +72 -27 libs/ui/KisDocument.cpp
M +2 -2 libs/ui/KisDocument.h
M +3 -2 libs/ui/KisImportExportUtils.h
https://invent.kde.org/graphics/krita/-/commit/706b558625d79f27cb8f774ea408b1540d08a719
--
You are receiving this mail because:
You are watching all bug changes.
