Project

General

Profile

Bug #11175

Crash on launch (OS X 10.8.5)

Added by Simon Robinson over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
09/26/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0.6
System:
Mac OS X
bitness:
64-bit
hardware architecture:
amd64/x86

Description

The latest darktable (2.0.6) crashes on launch for me. The crash report is attached.

History

#1 Updated by Tobias Ellinghaus over 3 years ago

Looks like a crash in OpenCL. Could you try disabling that in the preferences?

#2 Updated by Simon Robinson over 3 years ago

Sure - how can I do that directly? (e.g., without opening darktable, as it won't launch)

#3 Updated by Roman Lebedev over 3 years ago

$ darktable --disable-opencl

Or
$ echo "opencl=FALSE" >> ~/.config/darktable/darktablerc

#4 Updated by Simon Robinson over 3 years ago

Thanks - the --disable-opencl option worked, but modifying darktablerc didn't.

Is there anything else I can try to help you isolate the issue?

#5 Updated by Roman Lebedev over 3 years ago

Opencl is known to not work on OS X.

#6 Updated by Simon Robinson over 3 years ago

Ok - could this be a default option for the OS X build then?

#8 Updated by Simon Robinson over 3 years ago

Ok - any idea why that wasn't the case by default for me? (I just used the default OS X download).

It looks like --disable-opencl is doing something different to the option in darktablerc, which is what the link you gave seems to configure.

Just to reiterate, launching with --disable-opencl works, while the darktablerc options don't.

#9 Updated by Roman Lebedev over 3 years ago

Simon Robinson wrote:

Ok - any idea why that wasn't the case by default for me? (I just used the default OS X download).

It looks like --disable-opencl is doing something different to the option in darktablerc, which is what the link you gave seems to configure.

Correct.

Just to reiterate, launching with --disable-opencl works, while the darktablerc options don't.

Well. That means an opencl library crashes when we initialize opencl.
I have seen such cases before, not sure how it could possibly be handled without crashing.

#10 Updated by Simon Robinson over 3 years ago

Ok - so I suppose what I'm asking is: is there any way to make the OS X version use the --disable-opencl option by default?

#11 Updated by Rafa G. over 3 years ago

Simon Robinson wrote:

Ok - so I suppose what I'm asking is: is there any way to make the OS X version use the --disable-opencl option by default?

Maybe you had Darktable opened when you did

$ echo "opencl=FALSE" >> ~/.config/darktable/darktablerc

Because if it was the case when you closed Darktable it saved the configuration (overwriting your change).

I'm using a Mac and this property is working right (If I change it to TRUE or FALSE I can see enabled/disabled OpenCL checkbox at core section in settings)

#12 Updated by Simon Robinson over 3 years ago

I thought that too, but I've checked - all my darktablerc opencl-related values are false (presumably due to the configuration options Roman pointed to):

opencl=FALSE
opencl_async_pixelpipe=false
opencl_avoid_atomics=false
opencl_checksum=
opencl_device_priority=*/!0,*/*/*
opencl_library=
opencl_memory_headroom=300
opencl_memory_requirement=768
opencl_micro_nap=1000
opencl_number_event_handles=25
opencl_size_roundup=16
opencl_synch_cache=false
opencl_use_cpu_devices=false
opencl_use_pinned_memory=false

#13 Updated by Roman Lebedev over 3 years ago

I want to point out that --disable-opencl and echo "opencl=FALSE" >> ~/.config/darktable/darktablerc are two completely different things.
First completely disables everything about opencl, even initialization at start-up (which is faulty in this case), second simply disables dt from usin opencl devices to process images.

@Simon Robinson as for making --disable-opencl, i see multiple options:
1. just manually add each time you start dt from console
2. add it to the parameters of icon you use to start dt
3. re-compile dt with opencl disabled
4. remove all packages that are opencl-related (especially the ones containing icd in the name)
5. may be linux-specific: rm -rf /etc/OpenCL/vendors/*

#14 Updated by Simon Robinson over 3 years ago

Ok - it seems like there isn't an easy way to fix it permanently, so I went with option 2.
Many thanks for the help in solving this.

Also available in: Atom PDF

Go to top