cached(?) custom input color profile renders noise
I have placed a custom ICC profile for my camera in ~/.config/darktable/color/in/ and selecting it in Darktable works fine. When Darktable gets closed, while an image with such custom ICC profile is still selected/edited (Lighttable/Dark Room), it causes the following problem on next start of Darktable: images with that exact color profile assigned are rendered as color noise (see attached picture Darktable-post.png).
Work-around: open/select an image with embedded color matrix (like sRGB of JPG) before exiting Darktable.
#2 Updated by Hartmut Knaack over 3 years ago
There you go, also the sample DNG image.
For testing purpose, I also had copies of the same ICC file with different file names in ~/.config/darktable/color/in (all with the same checksum). So, when one of them resulted in such "noise", I could get proper results using a copy of that ICC file.
This also showed, that every image with that particular ICC file selected (which was last used before Darktable was closed, previously), would just render as noise. Images with other ICC files selected were rendered fine, switching to any other ICC file rendered fine.
It looks to me, that Darktable either tries to "cache" the decoded ICC file when closing and has problems to properly read it back later, or there can be problems loading the file on application start (race conditions?).