Summary: | Crash when scaling a very specific document. | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | wolthera <griffinvalley> |
Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | halla |
Priority: | NOR | Keywords: | drkonqi, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Document that crashes Krita when scaled to 72 dpi. |
Description
wolthera
2018-02-12 18:24:25 UTC
Created attachment 110571 [details]
Document that crashes Krita when scaled to 72 dpi.
Mind you, it's proly some division by 0 kind of error.
I don't get a crash... What are the exact settings for the scale image dialog? It must be yet another timing issue. The crash occurs after the image has been scaled, when the vector layer starts repainting: #6 KisUpdateScheduler::addSpontaneousJob (this=0x6000000ef, spontaneousJob=spontaneousJob@entry=0xa94bbc0) at /home/wolthera/krita/src/libs/image/kis_update_scheduler.cpp:209 #7 0x00007f80aef7af90 in KisImage::addSpontaneousJob (this=<optimized out>, spontaneousJob=spontaneousJob@entry=0xa94bbc0) at /home/wolthera/krita/src/libs/image/kis_image.cc:1440 #8 0x00007f80b3efd207 in KisShapeLayerCanvas::slotStartAsyncRepaint (this=0x11a10dc0) at /home/wolthe Can you still reproduce this crash with that document? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |