| Summary: | Assertion failure when trying to open a specific kra document | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | Andrei Alexeyev <akari> |
| Component: | File formats | Assignee: | Dmitry Kazakov <dimula73> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | dimula73, ghevan, halla |
| Priority: | NOR | Keywords: | regression |
| Version: | 4.2.6 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/kde/krita/commit/eda311fc215b8edd3c169be0e8fa8b12a69bca8b | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
Stack trace
Stack trace (v4.3.0-prealpha-451-g9894a20269) |
||
|
Description
Andrei Alexeyev
2019-09-24 13:23:05 UTC
On krita master f867486c5e835cd (macOS) I only got the assert once on opening but krita never crashed. I did try to reopen the file several times but the assert never showed again in the terminal. It is possible this bug is already fixed, or that maybe I need to paint in a certain way to trigger it as just waiting, or doing strokes on a new layer, does not cause the file to crash krita. Could you test if you can reproduce it in latest nightly krita? (Download krita next form the download page) I've built Krita from master the other day (v4.3.0-prealpha-451-g9894a20269), and unfortunately the crash still persists. Created attachment 122895 [details]
Stack trace (v4.3.0-prealpha-451-g9894a20269)
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. I can conform the crash. The terminal output is a bit crazy too: SAFE ASSERT (krita): "newLod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 659 SAFE ASSERT (krita): "newLod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 659 ASSERT (krita): "lod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 705 ASSERT (krita): "lod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 705 ASSERT (krita): "lod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 705 ASSERT (krita): "lod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 705 ASSERT (krita): "lod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 705 ASSERT (krita): "lod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 705 ASSERT (krita): "lod > 0" in file /home/boud/dev/krita/libs/image/kis_paint_device.cc, line 705 Re-raising signal for core dump handling. Aborted (core dumped) Git commit b18e3df355605b1332b74af494757121adda6d53 by Dmitry Kazakov. Committed on 11/11/2019 at 09:24. Pushed by dkazakov into branch 'master'. Fix crash when opening image with a Clone Layer and IP active All paint devices owned by layers should have default bounds set correctly. Otherwise, LoD generation will not work (and some other things, like wraparound and animation). M +12 -2 libs/image/kis_clone_layer.cpp M +2 -0 libs/image/kis_clone_layer.h https://invent.kde.org/kde/krita/commit/b18e3df355605b1332b74af494757121adda6d53 Git commit eda311fc215b8edd3c169be0e8fa8b12a69bca8b by Dmitry Kazakov. Committed on 11/11/2019 at 09:34. Pushed by dkazakov into branch 'krita/4.2'. Fix crash when opening image with a Clone Layer and IP active All paint devices owned by layers should have default bounds set correctly. Otherwise, LoD generation will not work (and some other things, like wraparound and animation). M +12 -2 libs/image/kis_clone_layer.cpp M +2 -0 libs/image/kis_clone_layer.h https://invent.kde.org/kde/krita/commit/eda311fc215b8edd3c169be0e8fa8b12a69bca8b |