Bug 469645 - Krita keeps crashing on a specific piece of artwork
Summary: Krita keeps crashing on a specific piece of artwork
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: * Unknown (show other bugs)
Version: 5.1.5
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-12 02:13 UTC by djdarius255
Modified: 2023-08-04 09:31 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
This is the crash log for krita giving you a look at what might be crashing it (563.17 KB, text/plain)
2023-05-12 02:13 UTC, djdarius255
Details
attachment-2428972-0.html (1.68 KB, text/html)
2023-05-17 01:43 UTC, djdarius255
Details
attachment-2941378-0.html (2.85 KB, text/html)
2023-05-22 23:50 UTC, djdarius255
Details

Note You need to log in before you can comment on or make changes to this bug.
Description djdarius255 2023-05-12 02:13:04 UTC
Created attachment 158873 [details]
This is the crash log for krita giving you a look at what might be crashing it

SUMMARY
Krita keeps crashing on a specific piece of artwork. I know this for a fact because after it crashed i worked on something else and it didnt crash but then went back to the old one and eventually it crashed again. im trying to figure out what might be the issue
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Halla Rempt 2023-05-12 07:09:09 UTC
Could you share the file with us? If it needs to stay private, please share with vurian@gmail.com (that's me...)
Comment 2 djdarius255 2023-05-17 01:43:06 UTC
Created attachment 159024 [details]
attachment-2428972-0.html

Do I send you the KRA file? I do not know how to directly send you the file

On Fri, 12 May 2023 at 03:09, Halla Rempt <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=469645
>
> Halla Rempt <halla@valdyas.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>            Severity|normal                      |crash
>          Resolution|---                         |WAITINGFORINFO
>            Platform|Compiled Sources            |Microsoft Windows
>                  CC|                            |halla@valdyas.org
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from Halla Rempt <halla@valdyas.org> ---
> Could you share the file with us? If it needs to stay private, please share
> with vurian@gmail.com (that's me...)
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Bug Janitor Service 2023-05-17 03:46:07 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 Tiar 2023-05-22 20:26:13 UTC
There are three ways how you can do it:
1) Easiest, but with size limit: you can visit https://bugs.kde.org/show_bug.cgi?id=469645 (this is the website for the bug report), there will be a list of Attachments. Underneath there is text "Add an attachment". Press it, then you'll see another page. There will be "Browse" button, click it, find the file that causes Krita to crash, add some text in Description field, and press "Submit".
2) You can share it on Google Drive (remember to add the viewing access for people having the link) or Dropbox or similar service.
3) If it's really private (or you can't show it to public because it's a commission for a client etc.), you can send an email from gmail to mentioned email address: vurian@gmail.com with the file as an attachment.

It's best to use (1) or (2) so all developers have access to it.
Comment 5 djdarius255 2023-05-22 23:50:56 UTC
Created attachment 159193 [details]
attachment-2941378-0.html

Here is the file
https://drive.google.com/file/d/1PWeE10XlcFdGWBU-Qz0bzZfnGWUfgXNW/view?usp=sharing
I believe it is crashing because after I finish the drawing and save it as
a png i go back to that same file and change it back to a kra file and draw
on it which then eventually crashes. but when i reopen krita it
doesnt crash again until i repeat what i just said.

On Mon, 22 May 2023 at 16:26, Tiar <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=469645
>
> Tiar <tamtamy.tymona@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>                  CC|                            |tamtamy.tymona@gmail.com
>
> --- Comment #4 from Tiar <tamtamy.tymona@gmail.com> ---
> There are three ways how you can do it:
> 1) Easiest, but with size limit: you can visit
> https://bugs.kde.org/show_bug.cgi?id=469645 (this is the website for the
> bug
> report), there will be a list of Attachments. Underneath there is text
> "Add an
> attachment". Press it, then you'll see another page. There will be "Browse"
> button, click it, find the file that causes Krita to crash, add some text
> in
> Description field, and press "Submit".
> 2) You can share it on Google Drive (remember to add the viewing access for
> people having the link) or Dropbox or similar service.
> 3) If it's really private (or you can't show it to public because it's a
> commission for a client etc.), you can send an email from gmail to
> mentioned
> email address: vurian@gmail.com with the file as an attachment.
>
> It's best to use (1) or (2) so all developers have access to it.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 6 Bug Janitor Service 2023-05-23 03:45:51 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 7 sh_zam 2023-06-27 14:33:14 UTC
I tried reproducing this but failed. Can you please do a screen recording so I know we are following the same steps?
Comment 8 Bug Janitor Service 2023-07-12 03:44:54 UTC
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
mark the bug 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!
Comment 9 vanyossi 2023-07-15 02:45:30 UTC
Please provide a detail step by step on how to reproduce the bug

What do you mean by "change it back to a kra file" after saving as png?, when I "Save as..." "png" I do not have to "revert back" to a kra as the image was never converted to a png, only a copy saved to that format. Without detail steps or a screen record we cannot know the exact steps you are following to make the bug appear.

Also please do not modify the bug status, that is for developers to determine
Comment 10 Bug Janitor Service 2023-07-31 03:44:57 UTC
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
mark the bug 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!
Comment 11 djdarius255 2023-08-04 04:21:29 UTC
I cannot reproduce the bug anymore cause my krita seems to work just fine now, i dont know what exactly happened sorry

> 
> On Jul 14, 2023, at 10:45 PM, vanyossi <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=469645
> 
> vanyossi <ghevan@gmail.com> changed:
> 
>           What    |Removed                     |Added
> ----------------------------------------------------------------------------
>         Resolution|---                         |WAITINGFORINFO
>                 CC|                            |ghevan@gmail.com
>             Status|CONFIRMED                   |NEEDSINFO
> 
> --- Comment #9 from vanyossi <ghevan@gmail.com> ---
> Please provide a detail step by step on how to reproduce the bug
> 
> What do you mean by "change it back to a kra file" after saving as png?, when I
> "Save as..." "png" I do not have to "revert back" to a kra as the image was
> never converted to a png, only a copy saved to that format. Without detail
> steps or a screen record we cannot know the exact steps you are following to
> make the bug appear.
> 
> Also please do not modify the bug status, that is for developers to determine
> 
> -- 
> You are receiving this mail because:
> You reported the bug.