Bug 352778

Summary: Using Contiguous Selection to Add Selections Throws an Exception
Product: [Applications] krita Reporter: Dennis Brown <vilesyn>
Component: ToolsAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version First Reported In: 2.9.7   
Target Milestone: ---   
Platform: Other   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Dennis Brown 2015-09-16 02:28:19 UTC
When selecting empty areas with the Contiguous Selection Tool to add to the selection, Krita crashes with an exception. 

Using VS15 to debug the process, and apologize if this is the incorrect way to gain verbose error logging. Could not find a way to accomplish with WIndows CLI. 

Reproducible: Always

Steps to Reproduce:
1. Draw some lineart, with some empty enclosed areas
2. Using the Contiguous Selection Tool, select the empty areas with the CST
3. Select until it crashes. Would happen within 2-3 tries using add or single select. Would crash on first select using 32-bit build (memory?).



Using: 2.9.7.6 x64 git #6577da7
Tested with: 2.9.7.6 x86 as well

Image being used is 7000x7000x8 dimensions, a common size for my illustrations, and Krita seems to be in 1.2/1.3GB memory use when crashing (Using x64). 

Debug output from VS15:

Exception thrown at 0x00007FF87E22C5FD (msvcr110.dll) in krita.exe: 0xC0000005: Access violation writing location 0x0000000000000000.

Unhandled exception at 0x00007FF87E22C5FD (msvcr110.dll) in krita.exe: 0xC0000005: Access violation writing location 0x0000000000000000.

These two errors will continue until I break.
Comment 1 Dennis Brown 2015-09-16 03:04:29 UTC
My apologies. This is a duplicate. I'm crashing any time I use over 1.3GB of memory with Krita x64 2.9.7.6, and even less with the x86 version.

Using Windows 10 x64 Professional. 

Here is the duplicate: https://bugs.kde.org/show_bug.cgi?id=349536
Comment 2 Dennis Brown 2015-09-16 03:05:12 UTC

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