Bug 369012

Summary: crash when playing animation when document's size is larger than 30M (approx)
Product: [Applications] krita Reporter: pedro.rocha62
Component: AnimationAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: crash CC: halla, scottpetrovic
Priority: NOR    
Version: 3.0.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:

Description pedro.rocha62 2016-09-18 21:15:16 UTC
I got to the limit of 30M though trial and error. That's anything larger than 2000 x 2000 pixels, 100 ppi.
On rare occasions it wont crash until the second or third time I press play.

Visual Studio debugging gave me this:
Unhandled exception at 0x000000005998EC7C (nvoglv64.dll) in krita.exe: Fatal program exit requested.

Sorry if that's not very useful. I'm not very tech savvy.


Reproducible: Always

Steps to Reproduce:
1. create a New document, predefined size "texture 2048 x 2048"
2. pick animation workspace
3. press Play/Pause button
it will crash even if I don't create any frames or draw anything

Actual Results:  
"Krita stopped working" crash

Expected Results:  
Play animation normally. 
Some lag would understandable with large files, but it shouldn't just crash

Windows 10 - 64 b
Krita 3.0.1 64 b (windows installer)
Nvidia GeForce GTX 750 Ti - driver 369.09
Comment 1 Halla Rempt 2016-09-19 12:29:38 UTC
Hi,

Thanks for your report. That crash happens in the nvidia driver -- nvoglv64.dll -- which suggests that we have a problem caching enough frames in GPU memory. How many frames does your animation file typically have?
Comment 2 pedro.rocha62 2016-09-22 06:55:01 UTC
Hello,

Sorry for the late response. In my testing I had the default number of frames, 100 I believe. Haven't really tested it with fewer frames.
Comment 3 Scott Petrovic 2016-09-28 02:19:12 UTC
I cannot get a crash with this. Followed the steps and tried toggling between play and pause. I have an NVIDIA GT650M
Comment 4 pedro.rocha62 2016-10-01 02:24:34 UTC
Update

Problem solved. It was a driver problem after all. Updated Nvidia to version 372.90 and haven't been able to reproduce to problem since, even with much larger files.

Thank you all for your help