darktable-org / darktable-org/darktable
Crash shortly after start
Nobody has claimed this yet.
- 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
I launch darktable, I can see my photos and a bunch of windows opening and closing, modules loading and then after 5-10 seconds it crashes.
It wasn't crashing month ago. It crashes now. I uninstalled it, installed latest version. It still crashes.
Steps to reproduce
- Launch the program
- Observe?
Expected behavior
not crash
Logfile | Screenshot | Screencast
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.4.0
What OS are you using?
Windows
What is the version of your OS?
Windows 11 Pro
Describe your system
Version: 25H2
OS build: 26200.7462
RAM: 32GB
CPU: Intel i5-12400F
GPU: NVIDIA RTX 4070 12GB
Driver version: 581.80
Are you using OpenCL GPU in darktable?
I dont know
If yes, what is the GPU card and driver?
NVIDIA RTX 4070 12GB 581.80
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
- I am using darktable to process my CR2 files to JPG
- darktable is installed on separate SSD, all images on HDD
- it crashes with
--disable-opencl - it doesn't crash with
--configdir "/tmp" - I do not use lua scripts
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached darktable-log.txt and reproducing the crash on Windows 11 with darktable 5.4.0. Compare normal startup with --disable-opencl and with --configdir "/tmp", since the report says the alternate config directory avoids the crash. Done means the startup failure has a confirmed cause and a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100