Closed lukkepcz closed 4 years ago
Does not reproduce on Linux (Intel® Xeon(R) CPU E3-1505M v6 @ 3.00GHz × 8).
I can reproduce on linux I will debug it
I wanted to write a "thank you" comment but I think I accidentaly closed the issue :( I'm sorry, how to undo that?
Addeneum: Guys, I'm both darktable and github newbie. Sorry for doing all the mess
I will debug it
Maybe related to the issue tackled in PR #4076
@upegelow Indeed! I'll check by building, but looking at the change of your PR I am quite confident it fixed this bug :-) Thank you!
Maybe a second thought on my commit is justified.
It deals with issues like in
However, could there be situations where 2 * mult is below 5 and we get out of bounds due to the inner loops?
I've just pulled and build, and the issue is gone.
2 * mult is below 5 for the scale 0 and the scale 1 (mult = 1 << scale), but I don't see how we can get out of bounds with the inner loop. In the inner loops, SUM_PIXEL_CONTRIBUTION_WITH_TEST is used whenever an out of bound index would be possible I think, and it tests and corrects it if needed
Sounds reasonable. Should be fine then.
Closing then, feel free to reopen if needed.
Describe the bug
Zooming in to 800% or 1600% when "denoise (profiled)" module is on with mode set to "wavelets" cause darktable to crash with "An unhandled exception occured" box showing up. The same behaviour observed when zoom is set to 1600% or 800% and "denoise (profiled)" module with the same mode is activated.
To Reproduce
Alternatively:
Expected behavior
Should not crash
Screenshots
Platform (please complete the following information):
Additional context
This is observable either with previously edited and with new raws. Backtrace file is usually almost empty, I also add another bactrace file generated after the same error but with content.
darktable_bt_68B0D0.txt darktable_bt_6FB0D0.txt