Bug 381176 - Krita crashes in the color selector dialog when you paste an #rrggbb color in the "color name" field
Summary: Krita crashes in the color selector dialog when you paste an #rrggbb color in...
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Color Selectors (show other bugs)
Version: 3.1.4
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-14 02:29 UTC by Joshua Kinard
Modified: 2017-09-26 17:29 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kritacrash.log (12.49 KB, text/plain)
2017-06-14 02:29 UTC, Joshua Kinard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Kinard 2017-06-14 02:29:56 UTC
Created attachment 106090 [details]
kritacrash.log

I am able to trigger a crash in Krita 3.1.4, on Windows Server 2008 R2 x64 (basically Windows 7, NT version is 6.1), by the following steps:

1. Open Krita.
2. Open any image (I used a small PNG from the "Fugue" icon set, v3.5.6).
3. Click on the color palette icon on the top toolbar to select a foreground/background color.
4. Click into the "Color name" field and select all existing text.
5. Paste a new #rrggbb color hex string already in the clipboard.
6. Click out of the field into any other field.
7. Crash.

I'll attach the kritacrash file as well, as the crash is happening in Qt5Widgets.dll, and I cannot locate a debug symbol file for that to use with the Windows Debugger.  Looks like the crash log has a pretty complete backtrace anyways.
Comment 1 Nicholas LaPointe 2017-06-22 11:19:09 UTC
Thanks for your report! I can reproduce the issue.
Pasting is actually unnecessary -- clicking the color name field and then any other field will cause the crash. However, the crash will only occur if a color has not yet been selected (using any color selector) in the running instance of Krita.
Comment 2 Halla Rempt 2017-09-26 17:29:34 UTC
I cannot reproduce this in master or in 3.3 anymore -- I think wolthera fixed this this summer.