Skip to content
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.

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

dt_dev_pixelpipe_change() should only be called if there is a change #18233

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jenshannoschwalm
Copy link
Collaborator

This avoids unnecessary and costly history locking and calls to dt_dev_pixelpipe_get_dimensions() if pipe->changed == DT_DEV_PIPE_UNCHANGED

Fixes #18232
Fixes #18014

@kofa73 @wpferguson would you both check please ?

This avoids unnecessary and costly history locking and calls to dt_dev_pixelpipe_get_dimensions()
if pipe->changed == DT_DEV_PIPE_UNCHANGED
@jenshannoschwalm jenshannoschwalm added bugfix pull request fixing a bug scope: performance doing everything the same but faster labels Jan 18, 2025
@kofa73
Copy link
Contributor

kofa73 commented Jan 18, 2025

I'm afraid I haven't been able to reproduce it after the initial report. I can maybe try again tomorrow.

@wpferguson
Copy link
Member

wpferguson commented Jan 18, 2025

Still doing it. I tried the slight zoom and pan suggestion and that didn't stop it. Had to go out to lighttable.

EDIT: The modules I applied were color calibration, tone equalizer, and lens correction.

@jenshannoschwalm
Copy link
Collaborator Author

@wpferguson could you do a log with -d pipe -d expose ?

@wpferguson
Copy link
Member

This time it happened when I loaded an image. A style is applied, then a color calibration preset and lens correction.

The log time the image was loaded is 244.2206. There were 5 images processed before that, so you can get a feel for what I'm doing.

loop_log.zip

@wpferguson
Copy link
Member

A new issue with the patch. Sometimes when I try and advance to the next image, the current image resets and loses all of it's edits.

@wpferguson
Copy link
Member

wpferguson commented Jan 19, 2025

This PR introduced a couple of other problems and didn't make any improvement to the existing problem.

EDIT: After going back to master, without this PR, I reproduced the errors that I though were caused by the PR. So, it seems that while the PR didn't fix anything, it didn't break anything worse than it already was.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix pull request fixing a bug scope: performance doing everything the same but faster
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Darktable stuck in processing loop darkroom display does not update when modules are applied.
3 participants