8000 Frequent crashes when exiting · Issue #18548 · darktable-org/darktable · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Frequent crashes when exiting #18548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
manuel-serrano opened this issue Mar 14, 2025 · 3 comments
Closed
1 task done

Frequent crashes when exiting #18548

manuel-serrano opened this issue Mar 14, 2025 · 3 comments
Labels
Fixed in master Has already been fixed in current master branch no-issue-activity

Comments

@manuel-serrano
Copy link

Is there an existing issue for this?

  • I checked and did not find my issue in the already reported ones

Describe the bug

Frequently (let's say in between 1/5 and 1/10) Darktable crashes when exiting it. I have the vague impression that this only occurs after making some complex editing, such as a complex retouch (complex in the sense, many areas are retouched).

The good news, is that no observable arm is done when it crashes. The sidecars are correctly stored and when I re-open darktable everything seem tidy and nothing is lost.

Steps to reproduce

Sorry, because I cannot really help, here (I wish I could). It happens to me when

  1. I open a file and do some significant manipulations (maybe involving many masks but I'm not sure).
  2. close the darktable window

Expected behavior

exiting nicely

Logfile | Screenshot | Screencast

I have to things for you, first the message displayed on the console and then the log file. I attach both of them
here.

stderr.txt

darktable_bt_YGKI32.txt

Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

5.0.1

What OS are you using?

Linux

What is the version of your OS?

Debian stable

Describe your system

Uname -a: Linux rumney 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/Linux

Darktable --vesion:

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

Compile options:
  Bit depth              -> 64 bit
  Debug                  -> DISABLED
  SSE2 optimizations     -> ENABLED
  OpenMP                 -> ENABLED
  OpenCL                 -> ENABLED
  Lua                    -> ENABLED  - API version 9.4.0
  Colord                 -> ENABLED
  gPhoto2                -> ENABLED
  GMIC                   -> ENABLED  - Compressed LUTs are supported
  GraphicsMagick         -> ENABLED
  ImageMagick            -> DISABLED
  libavif                -> DISABLED
  libheif                -> ENABLED
  libjxl                 -> ENABLED
  LibRaw                 -> ENABLED  - Version 0.22.0-Devel202403
  OpenJPEG               -> ENABLED
  OpenEXR                -> ENABLED
  WebP                   -> ENABLED
``

### Are you using OpenCL GPU in darktable?

Yes

### If yes, what is the GPU card and driver?

An nvidia card: GA107GLM [RTX A1000 Laptop GPU] [10DE:25B9], dont know how to get information about the driver

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

I understand that it will be difficult for you to make any real use of this bug report (except maybe the two log
files I provide) but I'm willing to help as much as I can. Please tell me if you want me to try something specific (I'm not afraid of using gdb to debug programs :-)
@jenshannoschwalm
Copy link
Collaborator

This is a well known issue with a lot of work been done, it's fixed in master :-)

@jenshannoschwalm jenshannoschwalm added the Fixed in master Has already been fixed in current master branch label Mar 14, 2025
@manuel-serrano
Copy link
Author

Ah wonderful! Thank you for your quick reaction. I have missed it when checking the bug tracker. Sorry about that.

@github-actions GitHub Actions
Copy link

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Fixed in master Has already been fixed in current master branch no-issue-activity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@manuel-serrano @jenshannoschwalm
0