darktable Crashing while operning files from one folder. Rest working fine

Darktable is crashing while reading files from only one folder, while leaving one error every time in the log i.e.

(darktable.exe:24812): GLib-CRITICAL **: 18:47:48.904: g_strlcpy: assertion ‘src != NULL’ failed
Magick: caught exception 0xC0000005 “Access violation”…

The full log is attached:
dt.log.txt (53.9 KB)

Here is the truncated log generated using darktable -d common

========================================
version: darktable 5.2.1
start: 2025-08-27 18:47:23

darktable 5.2.1
Copyright (C) 2012-2025 Johannes Hanika and other contributors.

Compile options:
  Bit depth              -> 64 bit
  Exiv2                  -> 0.27.7
  Lensfun                -> 0.3.4
  Debug                  -> DISABLED
  SSE2 optimizations     -> ENABLED
  OpenMP                 -> ENABLED
  OpenCL                 -> ENABLED
  Lua                    -> ENABLED  - API version 9.5.0
  Colord                 -> DISABLED
  gPhoto2                -> ENABLED
  OSMGpsMap              -> ENABLED  - map view is available
  GMIC                   -> ENABLED  - Compressed LUTs are supported
  GraphicsMagick         -> ENABLED
  ImageMagick            -> DISABLED
  libavif                -> ENABLED
  libheif                -> ENABLED
  libjxl                 -> ENABLED
  LibRaw                 -> ENABLED  - Version 0.22.0-Devel202502
  OpenJPEG               -> ENABLED
  OpenEXR                -> ENABLED
  WebP                   -> ENABLED

See https://www.darktable.org/resources/ for detailed documentation.
See https://github.com/darktable-org/darktable/issues/new/choose to report bugs.

     0.0001 [dt starting]
 C:\Program Files\darktable\bin\darktable.exe -d common
     0.0002 application_directory: C:\Program Files\darktable\bin
     0.0003 darktable.datadir: C:\Program Files\darktable\share\darktable
     0.0004 darktable.plugindir: C:\Program Files\darktable\lib\darktable
     0.0004 darktable.localedir: C:\Program Files\darktable\share\locale
     0.0005 darktable.sharedir: C:\Program Files\darktable\share
     0.0023 darktable.configdir: C:\Users\Farrukh\AppData\Local\darktable
     0.0027 darktable.cachedir: C:\Users\Farrukh\AppData\Local\Microsoft\Windows\INetCache\darktable
     0.0033 darktable.tmpdir: C:\Users\Farrukh\AppData\Local\Temp
     0.0033 new_xdg_data_dirs: (NULL)
     1.3480 [dt_worker_threads] using 7 worker threads
     1.5846 [dt_get_sysresource_level] switched to `default'
     1.5847   total mem:       32674MB
     1.5847   available mem:   16337MB
     1.5847   singlebuff:      255MB
     1.5847   mipmap cache:    4084MB
     1.8262 [opencl_init] opencl library 'OpenCL.dll' found on your system and loaded, preference 'default path'
     1.8868 [opencl_init] found 1 platform
[opencl_init] found 1 device

[dt_opencl_device_init]
   DEVICE:                   0: 'NVIDIA GeForce GTX 1660 Ti'
   CONF KEY:                 cldevice_v5_nvidiacudanvidiageforcegtx1660ti
   PLATFORM, VENDOR & ID:    NVIDIA CUDA, NVIDIA Corporation, ID=4318
   CANONICAL NAME:           nvidiacudanvidiageforcegtx1660ti
   DRIVER VERSION:           572.61
   DEVICE VERSION:           OpenCL 3.0 CUDA, SM_20 SUPPORT
   DEVICE_TYPE:              GPU, dedicated mem
   GLOBAL MEM SIZE:          6144 MB
   MAX MEM ALLOC:            1536 MB
   MAX IMAGE SIZE:           32768 x 32768
   MAX WORK GROUP SIZE:      1024
   MAX WORK ITEM DIMENSIONS: 3
   MAX WORK ITEM SIZES:      [ 1024 1024 64 ]
   ASYNC PIXELPIPE:          NO
   PINNED MEMORY TRANSFER:   NO
   AVOID ATOMICS:            NO
   MICRO NAP:                250
   ROUNDUP WIDTH & HEIGHT    16x16
   CHECK EVENT HANDLES:      128
   TILING ADVANTAGE:         0.000
   DEFAULT DEVICE:           NO
   KERNEL BUILD DIRECTORY:   C:\Program Files\darktable\share\darktable\kernels
   KERNEL DIRECTORY:         C:\Users\Farrukh\AppData\Local\Microsoft\Windows\INetCache\darktable\cached_v5_kernels_for_NVIDIACUDANVIDIAGeForceGTX1660Ti_57261
   CL COMPILER OPTION:       -cl-fast-relaxed-math
   CL COMPILER COMMAND:      -w -cl-fast-relaxed-math -DNVIDIA_SM_20=1 -DNVIDIA=1 -I"C:\Program Files\darktable\share\darktable\kernels"
   CL EXCEPTION:             DT_OPENCL_ONLY_CUDA
   KERNEL LOADING TIME:       0.0374 sec
[opencl_init] OpenCL successfully initialized. internal numbers and names of available devices:
[opencl_init]		0	'NVIDIA CUDA NVIDIA GeForce GTX 1660 Ti'
     2.0048 [opencl_init] FINALLY: opencl PREFERENCE=ON is AVAILABLE and ENABLED.
[opencl_init] opencl_scheduling_profile: 'default'
[opencl_init] opencl_device_priority: '*/!0,*/*/*/!0,*'
[opencl_init] opencl_mandatory_timeout: 1000
[opencl_update_priorities] these are your device priorities:
[opencl_update_priorities] 		image	preview	export	thumbs	preview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[opencl_update_priorities] 		image	preview	export	thumbs	preview2
[opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200
[opencl_update_priorities] these are your device priorities:
[opencl_update_priorities] 		image	preview	export	thumbs	preview2
[dt_opencl_update_priorities]		0	-1	0	0	-1
[opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[opencl_update_priorities] 		image	preview	export	thumbs	preview2
[opencl_update_priorities]		0	0	0	0	0
[opencl_synchronization_timeout] synchronization timeout set to 200

(darktable.exe:24812): GLib-CRITICAL **: 18:47:48.904: g_strlcpy: assertion 'src != NULL' failed
Magick: caught exception 0xC0000005 "Access violation"...

I think you should now copy half of the images into a new folder and continue importing until you find the offending image.

Btw, no need to start an identical conversation on GitHub unless it is first determined here there is an actual bug present.

1 Like

Just found a workaround.

Simply renamed that folder and everything started working fine. The old folder name was part of the DT’s database…

Now its working fine.
But still, the reason for its crashing must be investigated.

Ok…
I didn’t find that bug report there. I searched for the same before reporting the bug there, but didn’t find anything