[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 --- Comment #7 from Anna Medonosova --- Created attachment 116665 --> https://bugs.kde.org/attachment.cgi?id=116665&action=edit Python script that does not trigger the issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 --- Comment #6 from Anna Medonosova --- Created attachment 116664 --> https://bugs.kde.org/attachment.cgi?id=116664&action=edit Python script triggering the issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 --- Comment #5 from Anna Medonosova --- Created attachment 116663 --> https://bugs.kde.org/attachment.cgi?id=116663&action=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Anna Medonosova --- Thanks for supplying the whole plugin. I have run it and I can confirm the issue, it is present also on linux in git master. The python code triggers the following assert: ASSERT (krita): "!rhs.m_d->projectionUpdatesFilter" in file [..]/src/master/libs/image/kis_image.cc, line 340 How it happens: 1, the plug-in assigns the active document to self.document 2, then it runs self.document.scaleImage() and self.document.crop() 3, while operations from 2 are still running, the plug-in attempts to clone the document with self.document.clone() 4, assert is triggered I attach a simple script (401497_test.py) based on the plug-in code that reproduces the issue, to simplify testing. If I call Document::waitForDone() after scaleImage() and crop() calls, the assert is not triggered (demonstrated by 401497_test_nocrash.py). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 --- Comment #2 from Zlatko Masek --- Hi, Anna, No crash report as far as I can see. It doesn't give the crash dialog at all. I pushed the code to the repo so you can inspect: https://bitbucket.org/zmasek/krita-leaflet/src/master/ The code is still in development, but the line that breaks it is in app.py on line 56. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 Anna Medonosova changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||anna.medonos...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Anna Medonosova --- I am sorry, I cannot reproduce your issue. I tested in Krita 4.1.0 and 4.1.5 Portable 64-bit on Windows 10 with following code run in Scripter: - document = Krita.instance().activeDocument() new_image = document.clone() print(new_image.fileName()) - I assume that by “Krita turns off by itself” you mean it crashes. Could you please provide a backtrace from the crash? You can find instruction on how to do that at: https://docs.krita.org/en/reference_manual/dr_minw_debugger.html Could you also please provide a complete script that triggers the issue on your setup? -- You are receiving this mail because: You are watching all bug changes.
