Project

General

Profile

Bug #11731

darktable-2.3.0+898-ge47c49cfc-win64.exe

Added by Paul Herbert almost 2 years ago. Updated almost 2 years ago.

Status:
Closed: invalid
Priority:
Low
Assignee:
-
Category:
General
Target version:
Start date:
09/07/2017
Due date:
% Done:

0%

Affected Version:
git master branch
System:
Windows
bitness:
64-bit
hardware architecture:
amd64/x86

Description

I am running Windows 10 64-bit OS on the following Hardware:

Acer Aspire 8735 laptop
Intel Core2 Duo CPU T6600 @ 2.20GHz
4GB RAM
NVIDIA GEforce GT240M graphics processor with 1GB DDR3 RAM
500GB hard drive (329GB free)

The Windows version of Darktable installed - OK.
I started Darktable - it loaded - OK. I noticed that in core options, 'activate OpenCL support' was not available.
I imported a folder of Canon RAW files (*.CR2) and viewed them in Lighttable - OK.
Attempted to go into DarkRoom to process one image and got an error "An unhandled exception occurred"

I have attached the Backtrace log and screen shot of the error message.

darktable_bt_8XA65Y.txt Magnifier - Backtrace log file (7.15 KB) Paul Herbert, 09/07/2017 08:10 PM

20170907-darktable_exception_error.JPG - Screen shot of error message (23.9 KB) Paul Herbert, 09/07/2017 08:11 PM

History

#1 Updated by Tobias Ellinghaus almost 2 years ago

I am not sure about the actual crash, but you should run darktable-cltest and copy&paste the output. It might shed some light on why OpenCL isn't available for you.

#2 Updated by Tobias Ellinghaus almost 2 years ago

  • Affected Version changed from 2.2.5 to git master branch

#3 Updated by Paul Herbert almost 2 years ago

I ran darktable-cltest, results are below:

C:\Program Files\darktable\bin>darktable-cltest
[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 1
[opencl_init] opencl_library: ''
[opencl_init] opencl_memory_requirement: 768
[opencl_init] opencl_memory_headroom: 300
[opencl_init] opencl_device_priority: '*/!0,*/*/*'
[opencl_init] opencl_mandatory_timeout: 200
[opencl_init] opencl_size_roundup: 16
[opencl_init] opencl_async_pixelpipe: 0
[opencl_init] opencl_synch_cache: 0
[opencl_init] opencl_number_event_handles: 25
[opencl_init] opencl_micro_nap: 1000
[opencl_init] opencl_use_pinned_memory: 0
[opencl_init] opencl_use_cpu_devices: 0
[opencl_init] opencl_avoid_atomics: 0
[opencl_init]
[opencl_init] could not find opencl runtime library 'OpenCL.dll'
[opencl_init] no working opencl library found. Continue with opencl disabled
[opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is OFF.

#4 Updated by Paul Herbert almost 2 years ago

I have seen on the pixls forum that the error may be due to a space in the file path to darktable. I will reinstall darktable and try again.

#5 Updated by Paul Herbert almost 2 years ago

I installed darktable to C:\darktable and ran darktable-cltest. Unfortunately the OpenCL.dll runtime library was reported not found:

C:\darktable\bin>darktable-cltest
[opencl_init] opencl related configuration options:
[opencl_init]
[opencl_init] opencl: 1
[opencl_init] opencl_library: ''
[opencl_init] opencl_memory_requirement: 768
[opencl_init] opencl_memory_headroom: 300
[opencl_init] opencl_device_priority: '*/!0,*/*/*'
[opencl_init] opencl_mandatory_timeout: 200
[opencl_init] opencl_size_roundup: 16
[opencl_init] opencl_async_pixelpipe: 0
[opencl_init] opencl_synch_cache: 0
[opencl_init] opencl_number_event_handles: 25
[opencl_init] opencl_micro_nap: 1000
[opencl_init] opencl_use_pinned_memory: 0
[opencl_init] opencl_use_cpu_devices: 0
[opencl_init] opencl_avoid_atomics: 0
[opencl_init]
[opencl_init] could not find opencl runtime library 'OpenCL.dll'
[opencl_init] no working opencl library found. Continue with opencl disabled
[opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
[opencl_init] initial status of opencl enabled flag is OFF.

press any key to exit

C:\darktable\bin>

#6 Updated by Peter Budai almost 2 years ago

Based on the log you don't have OpenCL capable driver installed.

could not find opencl runtime library 'OpenCL.dll'

As I see you have an NVidia card - can you checek whether you have the latest NVidia driver installed from here:
https://www.geforce.com/drivers

#7 Updated by Paul Herbert almost 2 years ago

I did have the latest NVIDIA driver installed. However, I decided to to a clean install of the driver and after doing that, I ran GPU Caps Viewer which reported that OpenCL was available.

Then ran darktable-cltest and this also reported that OpenCL was available and completed normally.

I started darktable, and in core options, 'activate OpenCL support' was checked.

Images are displayed in lighttable, but more interesting - when I opened in image in darkroom I no longer get an unhandled exception error and I was able to edit the image as expected in darkroom. Progress...

#8 Updated by Peter Budai almost 2 years ago

Glad to hear that OpenCL works now for you. So one issue sorted out.
The reason you don't have a crash with OpenCL is that OpenCL and "non OpenCL" are different code paths. I assume there might be a bug in the "non OpenCL" code path nevertheless.

Asks:
  • Could you disable the OpenCL in the settings, and do the same edit which lead to a crash? Please let us know the results.
  • Also if crash happens with the non OpenCL way, would be great to have the picture in question uploaded, that might help us debugging.

After that you can enable OpenCL again and enjoy the performance benefits.

#9 Updated by Paul Herbert almost 2 years ago

I disabled OpenCL and opened the same image in darkroom that I think caused the crash - it opened without a problem. I checked with a range of images from the same folder - same result.

Because I had installed darktable in a non-default folder (C:\darktable), I removed darktable and re-installed into the default location (C:\Program Files\darktable).

After re-installation I was able to load darktable OK (though it seemed to load with OpenCL support not activated by default).

I can open the same image into darkroom with OpenCL support activated and not activated without any errors.

So I cannot re-create the crash I'm afraid.

#10 Updated by Peter Budai almost 2 years ago

OK thank you, then we can close the issue for now.

#11 Updated by Tobias Ellinghaus almost 2 years ago

  • Status changed from New to Closed: invalid

#12 Updated by Roman Lebedev almost 2 years ago

  • Target version set to 2.4.0

Also available in: Atom PDF