Interesting. However, based on the long bug history, I suspect that
there are multiple bugs in ufraw. One of them is almost certainly
related to threading since any description of needing to try several
times before it worked sounds like a threading issue.
For an application using OpenMP to thread an algorithm, a simple way
to see if an issue is related to threading is to set this environment
variable in the environment before starting the application:
If it then works consistently reliably, then the problem is due to
Someone should fix this dire issue:
"The submitted transforms array which contains the NULL transform is
created a stack frame above, in cmsCreateMultiprofileTransform(). The
function cmsCreateTransform() is called in some places without
checking its result (i.e. that it doesn't return NULL) which is then
put in the array."