[krita] [Bug 390725] Using setColorSpace on a document in python leads to safe-asserts and memory leaks.

https://bugs.kde.org/show_bug.cgi?id=390725 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[krita] [Bug 390725] Using setColorSpace on a document in python leads to safe-asserts and memory leaks.

https://bugs.kde.org/show_bug.cgi?id=390725 --- Comment #4 from Boudewijn Rempt --- Okay, it turns out that if one uses createDocument, then one needs to explicitly close the document in the same script, otherwise it'll be kept alive by Krita: d.close() -- You are receiving

[krita] [Bug 390725] Using setColorSpace on a document in python leads to safe-asserts and memory leaks.

https://bugs.kde.org/show_bug.cgi?id=390725 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org ---

[krita] [Bug 390725] Using setColorSpace on a document in python leads to safe-asserts and memory leaks.

https://bugs.kde.org/show_bug.cgi?id=390725 --- Comment #2 from wolthera --- Actually, disabling the use of setColorSpace doesn't solve the safeAssert, it just solves the refresh warning. The safe assert is caused by the following: 1. Open a document in python 2. get

[krita] [Bug 390725] Using setColorSpace on a document in python leads to safe-asserts and memory leaks.

https://bugs.kde.org/show_bug.cgi?id=390725 wolthera changed: What|Removed |Added Summary|Batch exporting a list of |Using setColorSpace on a