Bug 362421

Summary: [windows only] Crash when i creat a second animation file
Product: [Applications] krita Reporter: aquasx1
Component: AnimationAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: dimula73, griffinvalley, scottpetrovic
Priority: NOR    
Version: 3.0 Beta   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:

Description aquasx1 2016-04-28 14:59:00 UTC
If you create a new file on start up, I'll be a simple draw, which you can switch to animate. Once in animation, when you create a new file, it will also be an animation file, but the program will then crash. However, if you create two files and set one to animated, the other will also be an animation, but wont crash.

Reproducible: Always

Steps to Reproduce:
1.Create file
2.Set to animation
3.Create a new file

Actual Results:  
The program goes white a window appears. it says "krita.exe has stopped working" And that windows is searching for a solution, it then gives an option to either continue searching or close the program.

Expected Results:  
I suppose it should have two files with separate tabs that can be animations. Either that, or the new tab will be a drawing tab, not n animation tab.
Comment 1 Dmitry Kazakov 2016-05-03 12:51:32 UTC
I cannot reproduce that on Linux. And I didn't try on Windows yet.
Comment 2 Scott Petrovic 2016-05-07 15:24:49 UTC
I am on a Windows 10 box on the May 5 build (krita-3.0-Beta-master-962bfe1-x64). I cannot get this crash following the steps.

There were a few bug fixes recently with closing documents and openGL. could you try to grab the latest version and see if the same problem is still  happening?
Comment 3 aquasx1 2016-05-07 15:55:08 UTC
(In reply to Scott Petrovic from comment #2)
> I am on a Windows 10 box on the May 5 build
> (krita-3.0-Beta-master-962bfe1-x64). I cannot get this crash following the
> steps.
> 
> There were a few bug fixes recently with closing documents and openGL. could
> you try to grab the latest version and see if the same problem is still 
> happening?

I got the May 5 build and I am no longer able to reproduce the crash.
Comment 4 wolthera 2016-05-07 15:55:34 UTC
yay!