I’m using the latest darktable 2.7.0~git1923.16aca981b but I have been experiencing random crashes when browsing my library in lighttable for a while now (can’t really remember the git version, but it’s a couple of weeks now).
I cannot reproduce or understand the issue so I have been just carrying on hoping that the latest commit would fix these crashes.
I am now running darktable-generate-cache and it crashed again with the scary segmentation fault; I’m seeing these error msg that I also remember seeing during all the instances when DT would crash:
[dt_ioppr_check_duplicate_iop_order] modules tonecurve (39,000000) and shadhi (39,000000) have the same iop_order
[dt_ioppr_check_duplicate_iop_order] modules shadhi (39,000000) and bilat (39,000000) have the same iop_order
[dt_ioppr_check_duplicate_iop_order] modules bilat (39,000000) and velvia (39,000000) have the same iop_order
[dt_ioppr_check_duplicate_iop_order] modules tonecurve (39,000000) and shadhi (39,000000) have the same iop_order
[dt_ioppr_check_duplicate_iop_order] modules shadhi (39,000000) and bilat (39,000000) have the same iop_order
[dt_ioppr_check_duplicate_iop_order] modules bilat (39,000000) and velvia (39,000000) have the same iop_order
Segmentation fault (core dumped)
There has been a lot of work done on fixing pipe order issues in the last couple of days, please check the project’s issues and pull requests for the most recent status. Seems that there is a solution but not merged yet, maybe you can test the PR directly?
Thought it was just me…posted an issue on git…darktable-log.txt (4.2 MB) I think the xmp files are not in good order and scrolling in lightable and or film strip of DT triggers it fairly early on for me after opening the program