Bug 362714 - going to frame 1, krita closes when onion skin is activated
Summary: going to frame 1, krita closes when onion skin is activated
Status: RESOLVED NOT A BUG
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 3.0 Beta
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-05 18:59 UTC by Zkoyllar
Modified: 2019-09-05 08:21 UTC (History)
4 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Zkoyllar 2016-05-05 18:59:58 UTC 
The program closes whenever I activate the onion skin and go to the first frame. 

Steps I follow. 
Go to timeline


Reproducible: Always

Steps to Reproduce:
1.I create first frame. 
2.I create second frame. 
3.Activate onion skin.
4.Go to first frame. 
5.Krita closes without showing any kind of message. 

Actual Results:  
Krita closes.

Expected Results:  
Allow to see frame one when onion skin is activated. 

This has happened since the lastest 3 builds for windows.
Comment 1 Scott Petrovic 2016-05-07 15:16:15 UTC 
I am on Windows 10 and cannot get this crash to happen on the May 5 build (krita-3.0-Beta-master-962bfe1-x64). Can anyone else get this crash to happen?

If you have been testing earlier builds, maybe there is something odd in the config file that is messing it up. Clearing that could potentially help.
Comment 2 Nimthora 2016-05-25 13:22:24 UTC 
The steps seems to work fine for me on Windows 10 as well, using build (krita-3.0-Beta-master-25ecbaf-x64).
Comment 3 Zkoyllar 2016-05-25 15:19:21 UTC 
I tried the software in different computers and turns out I needed to update soem windows components. 
I thought it was a bug at the begining because older versions worked without issues.
Comment 4 Halla Rempt 2016-05-25 15:46:20 UTC 
Thanks for checking back!
Comment 5 nik.hallstrom 2016-06-01 14:39:23 UTC 
Confirming bug is in the stable release of Krita 3.0.