darktable-org / darktable-org/darktable

Issue with --opencl-migrate

Open
#21,799 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OpenCL
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

When using --OpenCL-migrate, darktable opens in lightable and shows images in collections but, when trying to open an image dt crash.

Steps to reproduce

Start darktable from terminal with
/Applications/darktable.app/Contents/MacOS/darktable -d pipe --opencl-migrate

Expected behavior

dt should open the image in darkroom. When running /Applications/darktable.app/Contents/MacOS/darktable -d pipe -d opencl all is working as expected as seen in the log file first part, at the end is the log of the crash

Logfile | Screenshot | Screencast

-d opencl & --opencl-migrate.txt

Commit

darktable-5.7.0+434.gc19e88f8d8-x86_64.dmg

Where did you obtain darktable from?

GitHub nightly

darktable version

darktable-5.7.0+434

What OS are you using?

Mac

What is the version of your OS?

0S 26.5.2

Describe your system

iMac intel, i7, AMD Radeon Pro 5700 XT 16GB/ 64 GB DDR4

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

The sample image that I use for testing is a .NEF from Nikon D810 that I tried to drop here but is not supported

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the crash with /Applications/darktable.app/Contents/MacOS/darktable -d pipe --opencl-migrate and inspect the attached OpenCL log. Compare it with the working command using -d opencl, then trace the failure reached when opening a .NEF image in darkroom. Done means the image opens without a crash while migration is enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
computer-graphics, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.