|Summary:||Isolate Layer Crash|
|Product:||[Applications] krita||Reporter:||Bollebib <kwadraatnope>|
|Component:||General||Assignee:||Dmitry Kazakov <dimula73>|
|Latest Commit:||https://invent.kde.org/kde/krita/commit/4f346c1830867d590604753ce3f5dc7acb409a33||Version Fixed In:|
|Attachments:||Log File of Crashes|
Description Bollebib 2019-06-16 15:17:05 UTC
https://www.youtube.com/watch?v=oDdbcO9shHc using isolate layer can trigger a crash it takes a little while of going back and forward,up and down layers, and doing some manipulations it can take a little while but it does crash consistently
Comment 1 Halla Rempt 2019-06-20 09:03:51 UTC
Could use the portable zip + debug package so we can have a crash log next time this happens? See https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#using-the-debug-package . It's pretty hard to reproduce, and I haven't succeeded yet.
Comment 2 Bollebib 2019-06-20 13:36:22 UTC
I've already done that and mentionned on IRC that it didnt leave me a chat log I have no idea what else can be done. Maybe that live monitoring tool?
Comment 3 Bug Janitor Service 2019-06-21 04:33:08 UTC
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.
Comment 4 Halla Rempt 2019-06-21 12:31:34 UTC
Ah, yes, now I remember. I was talking about teamviewer.
Comment 6 Dmitry Kazakov 2019-07-17 13:35:06 UTC
The problem happens somewhere in animation cache regeneration algorithm. To workaround an issue you should disable "Update animation cache in background" option in the performance settings.
Comment 7 Dmitry Kazakov 2019-08-02 15:09:58 UTC
Git commit dea45823ccc2ad1cd5c72192314a42b4ffb6fddd by Dmitry Kazakov. Committed on 02/08/2019 at 15:09. Pushed by dkazakov into branch 'master'. Don't try to generate LoD cache when the source device is empty Our "empty" devices have a weird extent (qintmax, qintmax, 0, 0), which makes the LoD generation algorithm crash when it tries to read from qintmax-tile. So we should just check it. M +2 -0 libs/image/kis_paint_device.cc https://invent.kde.org/kde/krita/commit/dea45823ccc2ad1cd5c72192314a42b4ffb6fddd
Comment 8 Dmitry Kazakov 2019-08-14 16:41:49 UTC
Git commit 4f346c1830867d590604753ce3f5dc7acb409a33 by Dmitry Kazakov. Committed on 14/08/2019 at 16:21. Pushed by dkazakov into branch 'krita/4.2'. Don't try to generate LoD cache when the source device is empty Our "empty" devices have a weird extent (qintmax, qintmax, 0, 0), which makes the LoD generation algorithm crash when it tries to read from qintmax-tile. So we should just check it. M +2 -0 libs/image/kis_paint_device.cc https://invent.kde.org/kde/krita/commit/4f346c1830867d590604753ce3f5dc7acb409a33