If two or more new images are created, and if said images have a color depth greater than 8 bit, selecting a color with the "Specific Color Selector", painting something, and repeating these steps while switching between both images created, will cause Krita to crash. The Krita process will remain the background and prevent other instances from being opened unless it's forcibly terminated. Reproducible: Always Steps to Reproduce: 1. Open the new image dialog 2. Select 16-bit depth or more, linear gamma color profile 3. Create image 4. Repeat steps [1-3] one or more times 5. Select a color using the "specific color selector" docker 6. Paint something 7. Switch to another image created 8. Repeat steps [5-8] several times Actual Results: 1. The specific color selector resets to RGB (0,0,0) every time the user switches to another opened image. 2. Krita will eventually crash. The process will remain active and will prevent other instances from being created. Expected Results: No crash should happen; the specific color selector should retain the selected color. Krita x64 2.9.7.5 Windows 10 Pro 64-bit
Hi Eiko, I haven't yet been able to reproduce the crash, but I do see the resetting to black. I'm going to take a look.
Git commit 891cd485c85d4013ac731628e2ec29b8753b32f1 by Boudewijn Rempt. Committed on 12/09/2015 at 09:26. Pushed by rempt into branch 'calligra/2.9'. M +5 -1 krita/plugins/extensions/dockers/specificcolorselector/kis_specific_color_selector_widget.cc http://commits.kde.org/calligra/891cd485c85d4013ac731628e2ec29b8753b32f1
Git commit d0b58f0cc3e44c10fd3bdc2587a53219f693f1ce by Boudewijn Rempt. Committed on 12/09/2015 at 09:27. Pushed by rempt into branch 'master'. M +5 -1 krita/plugins/extensions/dockers/specificcolorselector/kis_specific_color_selector_widget.cc http://commits.kde.org/calligra/d0b58f0cc3e44c10fd3bdc2587a53219f693f1ce