| Summary: | *Sometimes* crashes on loading files via drag and drop | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Lake <winter.wulf> |
| Component: | File formats | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | halla, info |
| Priority: | NOR | ||
| Version First Reported In: | 3.0 Release Candidate | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | http://commits.kde.org/krita/ea7592e93feadb2080a6c48ca6ce44b88ee3230e | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Lake
2016-05-22 22:35:21 UTC
*** Bug 363470 has been marked as a duplicate of this bug. *** Must be timing dependent: see also the duplicate bug. Git commit ea7592e93feadb2080a6c48ca6ce44b88ee3230e by Friedrich W. H. Kossebau. Committed on 27/05/2016 at 10:05. Pushed by kossebau into branch 'master'. Fix double-deletion crash on destruction of KisNode with KisNodeProgressProxy Summary: The emission of the signal KisNodeProgressProxy::percentageChanged due to KisBusyProgressIndicator::endUpdatesBeforeDestroying() KisBusyProgressIndicator::Private::stopProgressReport() KisNodeProgressProxy::setRange(int, int) resulted in a temporary KisNodeSP being created, which called ref() and deref() on the KisNode object, whose KisShared part already was at 0 ref count, which results in deref() to trigger another delete call on the KisNode. Related: bug 363470 Fixes T2393 Test Plan: KisFileLayerTest no longer fails, other tests still as before. Reviewers: #krita:_next, rempt, dkazakov Differential Revision: https://phabricator.kde.org/D1695 M +12 -6 libs/image/kis_busy_progress_indicator.cpp M +13 -2 libs/image/kis_busy_progress_indicator.h M +2 -1 libs/image/kis_node.cpp M +6 -0 libs/image/kis_node_progress_proxy.cpp M +8 -0 libs/image/kis_node_progress_proxy.h http://commits.kde.org/krita/ea7592e93feadb2080a6c48ca6ce44b88ee3230e |