Bug 425199 - Program closed down after I click on a tool
Summary: Program closed down after I click on a tool
Status: RESOLVED DUPLICATE of bug 424037
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Other Other
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-10 18:46 UTC by Lauren
Modified: 2020-08-15 22:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Backtrace included here - wasn't able to add it in the comment (162.50 KB, text/plain)
2020-08-10 18:46 UTC, Lauren
Details
attachment-14640-0.html (1.76 KB, text/html)
2020-08-11 20:16 UTC, Lauren
Details
attachment-18647-0.html (1.39 KB, text/html)
2020-08-12 15:36 UTC, Lauren
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lauren 2020-08-10 18:46:04 UTC
Created attachment 130765 [details]
Backtrace included here - wasn't able to add it in the comment

SUMMARY
I was trying to make an animation, I clicked on the move tool and the program stopped responding for a moment before closing itself, no error message appeared.
This happened several more times, the cause differed but mainly when I tried to click on something.
Same thing happened when using a normal paint workspace.
Sometimes it works fine for a bit.

STEPS TO REPRODUCE
1. Right-Click on timeline
2. Set Start Time
3. Scroll up
4. Right-Click

OBSERVED RESULT
blue loading circle appears
Krita closes

EXPECTED RESULT
Shouldn't close

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

ADDITIONAL INFORMATION
Comment 1 Lauren 2020-08-10 18:47:59 UTC
Backtrace was attached
Comment 2 wolthera 2020-08-10 18:50:44 UTC
Looks like it is crashing consistently in the animation frame cache (That's where Krita is keeping the precalculated frames).

Like, my best guess is that Krita is trying to calculate the frames, but then scrubbing happens, and krita can't figure out how to access that frame.
Comment 3 Ahab Greybeard 2020-08-10 19:05:29 UTC
Lauren has crashes when using a non-animated workspace

Which version of krita are you using?
Where did you get it from? (the official website, Windows Store, Steam?)

Has this happened since you installed it and started using it or has it started to happen recently?
Did it happen with any previous versions you may have used?

Can you do Help -> Show systen information for bug reports
and paste the entire output in a comment here?

If you dowload, Extract and run the Stable portable .zip package:
https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/
does it show the same behaviour?
Comment 4 Eoin O'Neill 2020-08-11 18:48:58 UTC
Hi Lauren,

There's a chance that this issue is related to an existing bug that has been fixed and ready for the next major release. Could you please try to download Krita Plus and report back whether this crash continues to occur?

Additionally, on the current version of Krita, can you try to enable graphics acceleration and report whether or not changing that value has changed?
Comment 5 Lauren 2020-08-11 20:16:24 UTC
Created attachment 130797 [details]
attachment-14640-0.html

Enabling graphics acceleration seems to have fixed the problem, I'll go
ahead and download Krita Plus just in case though.
How exactly do I do that?

On Tue, Aug 11, 2020 at 7:49 PM Eoin O'Neill <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=425199
>
> Eoin O'Neill <eoinoneill1991@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |eoinoneill1991@gmail.com
>
> --- Comment #4 from Eoin O'Neill <eoinoneill1991@gmail.com> ---
> Hi Lauren,
>
> There's a chance that this issue is related to an existing bug that has
> been
> fixed and ready for the next major release. Could you please try to
> download
> Krita Plus and report back whether this crash continues to occur?
>
> Additionally, on the current version of Krita, can you try to enable
> graphics
> acceleration and report whether or not changing that value has changed?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 6 Eoin O'Neill 2020-08-11 21:59:50 UTC
Hi again Lauren,

You can download krita plus from krita.org from our stable nightly build available here: 

https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/

Click on one of the download links that looks like the 

`krita-nightly-x64-v4.3.0-beta2-533-ga7cf99a7c0-setup.exe`

This will be an installer for the new beta version of krita which will hold you over until the next stable version releases.
Comment 7 Bug Janitor Service 2020-08-12 04:33:17 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 8 Lauren 2020-08-12 15:36:54 UTC
Created attachment 130825 [details]
attachment-18647-0.html

Thank You very much for the help

On Tue, Aug 11, 2020 at 10:59 PM Eoin O'Neill <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=425199
>
> --- Comment #6 from Eoin O'Neill <eoinoneill1991@gmail.com> ---
> Hi again Lauren,
>
> You can download krita plus from krita.org from our stable nightly build
> available here:
>
> https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/
>
> Click on one of the download links that looks like the
>
> `krita-nightly-x64-v4.3.0-beta2-533-ga7cf99a7c0-setup.exe`
>
> This will be an installer for the new beta version of krita which will
> hold you
> over until the next stable version releases.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 9 Eoin O'Neill 2020-08-15 22:21:05 UTC
No worries Lauren, glad I could help.

I am closing this bug for now as it seems like this is resolved.

*** This bug has been marked as a duplicate of bug 424037 ***