https://bugs.kde.org/show_bug.cgi?id=411081
--- Comment #6 from Dmitry Kazakov <dimul...@gmail.com> --- Git commit 2ffdc5b070522bf1df73844ff47f525cb4a9262c by Dmitry Kazakov. Committed on 20/08/2019 at 16:10. Pushed by dkazakov into branch 'master'. Fix ConcurrentMap::migrationInProcess() to handle initialization value (0) properly Job coordinator of the table may have three states: 1) jobCoordinator == 0: the table was initialized, but no migration has ever been started for this table 2) jobCoordinator > 1: a table migration is in progress right now. The caller should join *jobCoordinator to help finishing the migration. 3) jobCoordinator == 1: the table migration has been finished. It means that the table doesn't have any values in it anymore. The patch actually fixes the map to consider case 1 as a situation, when there is no migration. M +1 -1 libs/image/3rdparty/lock_free_map/concurrent_map.h https://invent.kde.org/kde/krita/commit/2ffdc5b070522bf1df73844ff47f525cb4a9262c -- You are receiving this mail because: You are watching all bug changes.
