Bug #11976

windows 10, unhandled exception when double click on photo in lighttable

Added by Wim Spijker over 1 year ago. Updated about 1 month ago.

Target version:
Start date:
Due date:
% Done:


Affected Version:
hardware architecture:


See report in attachment. It happens not always, so difficult to find I think. When opening the same pohot in de darkroom filemanager, all goes well.
I hope this information is useful for you.

darktable_bt_35CIDZ.txt Magnifier (7.06 KB) Wim Spijker, 01/29/2018 11:47 AM

history stack.JPG - history stack (13.8 KB) Wim Spijker, 01/29/2018 12:54 PM

2018-01-26-WIM_3085.CR2.xmp - crash (3.53 KB) Wim Spijker, 01/29/2018 01:27 PM

2018-01-26-WIM_3085_01.CR2.xmp - no crash (3.19 KB) Wim Spijker, 01/29/2018 01:28 PM

2018-01-26-WIM_3085.CR2 (27 MB) Wim Spijker, 01/30/2018 10:39 AM


#1 Updated by Tobias Ellinghaus over 1 year ago

Thanks, that is a bug we have several reports for already. So far we haven't been able to figure out what's going on. So if you can find any way to reliably reproduce it we would be more than happy to hear about it! Or maybe it's depending on the modules used on an image? Masks used? Multiple instances of modules? Something else?

#2 Updated by Wim Spijker over 1 year ago

It happens when starting darktable, going to lighttable and double click on specific photo (but taken from the same camera as all other photos in that folder). When clicking on an other photo, all goes well. When returning to lighttable and again open the same "specific photo", there is no error. So mysterious, but repeatable with that photo.

In the bug file maybe this helps: darktable.exe caused an Access Violation at location 000000006A481C71 in module librawprepare.dll Reading from location 000000000C8D2000.

The history stack is attached.

Then I duplicated the photo, the same thing happens, also crash on the duplicate

Then I delete history stack line 6, still the same problem.

Then I delete history stack line 5 (crop and rotate), now I can open the photo from lighttable without problem. So maybe it is the crop and rotate module?

Now I did the crop again (aspect square), and yes the problem is back.

To be sure I tried it once again. No error at all, I tried it about 5 times. No crash. So now I don't know how to go further.

The original photo still gives the crash.
Crop and rotate:
flip none
angle -0,70
keystone none
automatic cropping yes
aspect square
guides: rules of thirds
flip guides both

When I select the "crop and rotate" then it appears in the history stack. When I make a new selection and double click on it to see the result, another crop and rotate line is added in the history stack. Is that normal? When "compress history stack" the 2 lines becomes one.

I hope this helps you to find the bug, but I think it is difficult, because it is not good repeatable.

Best regards

#3 Updated by Peter Budai over 1 year ago

Any chance to upload the photo itself?

#4 Updated by Wim Spijker over 1 year ago

Peter Budai wrote:

Any chance to upload the photo itself?

Here is the photo!

#5 Updated by Anonymous over 1 year ago

Spam deleted

#6 Updated by David Houlder over 1 year ago

Possible duplicate of #11596 #11793 #11831 #11756

#7 Updated by martin garix about 1 month ago

How to get help in windows 10 ( now here the fully guide and help you any window issue,and i am sure you try to understand this all simple process.

Also available in: Atom PDF