darktable-org / darktable-org/darktable

Crashes at master branch

Open
#19,573 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity understood: unclear
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

Darktable shows the following log and exists:

/home/mikesolar/Projects/darktable/cmake-build-debug/bin/darktable
     0.6302 [dt_init] ERROR: can't init develop system, aborting.
Steps to reproduce
  1. Clone the darktable
  2. Compile it with CLion, gcc and CMake.
  3. Open it in CLion, and crashed.
Expected behavior

No response

Logfile | Screenshot | Screencast

/home/mikesolar/Projects/darktable/cmake-build-debug/bin/darktable
0.6302 [dt_init] ERROR: can't init develop system, aborting.

Commit

96a64902f5abf201dd595cad617afbb414513095

Where did you obtain darktable from?

self compiled

darktable version

96a64902f5

What OS are you using?

Linux

What is the version of your OS?

Arch Linux with GTK 3.24.51-1

Describe your system

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

RTX 4060Ti 16GB, NVIDIA Driver Version 580.95.05

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

Occurs at line 1847 at darktable.c:

 if(!darktable.develop)
  {
    dt_print(DT_DEBUG_ALWAYS, "[dt_init] ERROR: can't init develop system, aborting.");
    darktable_splash_screen_destroy();
    return 1;
  }

GDB shows:

(gdb) print darktable.develop
$1 = (struct dt_develop_t *) 0x0

And:
Image

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

Start at darktable.c:1847 and reproduce the crash using the self-compiled Arch Linux build described in the issue. Use the reported GDB state of darktable.develop and inspect the initialization path leading to the abort. Done means darktable.develop is initialized and darktable starts instead of exiting with the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cmake
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.