Bug 399899 - CRASH on unselecting after using color mask ???
Summary: CRASH on unselecting after using color mask ???
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Tools/Colorize (show other bugs)
Version: 4.1.5
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-16 20:30 UTC by zeusex81
Modified: 2018-10-21 12:01 UTC (History)
2 users (show)

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

Attachments
(Video example) (1.39 MB, video/mp4)
2018-10-16 21:34 UTC, mvowada 		Details
(GDB - Appimage) (69.94 KB, text/plain)
2018-10-16 21:37 UTC, mvowada 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description zeusex81 2018-10-16 20:30:32 UTC 
STEPS TO REPRODUCE
1. open some lineart
2. select color mask tool and use it
3. update and convert mask to painting layer
4. select opaque
5. unselect with Ctrl+Shift+A
6. boom

ADDITIONAL INFORMATION
You must unselect with the shortcut while the color mask tool is still selected.
Comment 1 Halla Rempt 2018-10-16 20:35:00 UTC 
I'm sorry... But I cannot reproduce that crash. Could you check https://docs.krita.org/en/KritaFAQ.html?highlight=mingw and make a backtrace?
Comment 2 mvowada 2018-10-16 21:34:46 UTC 
Created attachment 115689 [details]
(Video example)

(Krita 4.1.5 - Ubuntu 14.04)

Yes, if I had set a color to Transparent in the options (see video). Note that the nightly Krita is not affected:

    1. "Colorize Mask Tool" options > set a color to "Transparent"
    2. apply
    3. select opaque
    4. "CTRL + SHIFT + A"

Actual Results: SIGSEGV signal
Comment 3 mvowada 2018-10-16 21:37:52 UTC 
Created attachment 115690 [details]
(GDB - Appimage)

(I had to copy paste only a few lines since it returned an endless output)
Comment 4 mvowada 2018-10-16 21:38:35 UTC 
Confirming?
Comment 5 Halla Rempt 2018-10-21 12:01:12 UTC 
We probably aren't going to release a new 4.1, so if it's already fixed in master, then we can close the issue.