Darktable: Current DT build on windows doesnt start app.

Created on 17 Sep 2019  Â·  21Comments  Â·  Source: darktable-org/darktable

Describe the bug
A clear and concise description of what the bug is.
Built a clean darktable-2.7.0+1727~g0672f79d0-win64.exe today, installed it first as upgrade to my previous 2.7.xxxx build. Started app , popped the initial dt window , the one before the app actually starts. That window disappeared and nothing started.

Then I installed again and this time I used the clean install, same thing , DT doesnt start.

Ran dt executable with the -d all command line option , no log got created C:Users[username]\AppData\Local\Microsoft\Windows\INetCache\darktable\darktable-log.txt

All 21 comments

I uninstalled and did a clean install, got the log file.

darktable-log.txt

Uninstall does not remove the files
darktablerc
data.db
keyboardrc
keyboardrc_default
library.db

Once I deleted those the app started fine.
`
Once started importing existing folder that contains raw files and their xmps crashes DT, you can see 3 to 4 imported and then it crashes. There is something really wrong with this build.
6.365989 [sql] F:/msys64/home/chill/darktable/src/common/history.c:997, function dt_history_check_module_exists(): prepare "SELECT imgid FROM main.history WHERE imgid= ?1 AND operation = ?2"
6.361991 [HiDPI] setting ppd to 1.000000
6.367990 [run_job-] 03 278124711.775516 6.370990 load image 9 mip 0 | queue: 1 | priority: 46.371987
6.366989 [sql] F:/msys64/home/chill/darktable/src/common/history.c:997, function dt_history_check_module_exists(): prepare "SELECT imgid FROM main.history WHERE imgid= ?1 AND operation = ?2"
6.370990 [screen resolution] setting the screen resolution to 96.000000 dpi
6.368990 [sql] F:/msys64/home/chill/darktable/src/common/history.c:997, function dt_history_check_module_exists(): prepare "SELECT imgid FROM main.history WHERE imgid= ?1 AND operation = ?2"
6.369988 [sql] F:/msys64/home/chill/darktable/src/common/history.c:997, function dt_history_check_module_exists(): prepare "SELECT

`

confirmed. after deleting the library.db darktable starts, initial importing one picture into the library is ok, two or more files results in a termination.
Addition: even one single file in library.db results in a termination after reopening darktable

I have had to roll back to an older install that works.
darktable-2.7.0+1735~gc80f4156f-win64 too crashes on startup if the database is still around from an older install. Deleting the config dir results in app starting, but crashes on import.

The last one that worked was 2.7.0.1687

Same issue just built it and it is not opening direct to an error code ...running Win10Pro on intel core i7
Erro 0xc0000142

Have also been testing, removing the database (library.db plus data.db) and started importing files, first one then some 20 and then thousands. Not a single problem at all.
tested two versions
1) c80f415 plus pr# 2955 on fedora 30
2) master 0954325
Both went just as expected, masks import, all modules activated as desired. BTW - i does not matter having xmp files or not.

What i couldn't test: I have no old database at hand.

Mmm, don't know right now. Any more details?

@jenshannoschwalm
Here are my config file that were being used on an upgrade, maybe it helps.
config.zip

I can see that your library.db contains signs of an old history. But on first sight i can't identify a database corruption.
You describe a situation where you import just one file to an empty database and can't use dt later onwards.
Could you share such an image file+xmp plus the config data as you sent right after that import?

@jenshannoschwalm
I did not try one file, that was @MStraeten .
I import folder that has sub folders. (image of folder structure and images+xmp imported before crash are in the zip file). I had to look at the library db to see which ones were in there and I have shared the ones that were in the library.db images table.
Please grab it from the drop box link.
https://www.dropbox.com/sh/6b905xltzknxkk7/AACiLsjK7qdGA4yXs1Td3lA6a?dl=0

C:\Program Files\darktable\bin>darktable.exe --version
this is darktable 2.7.0+1775~g060abe657
copyright (c) 2009-2019 johannes hanika
[email protected]

compile options:
bit depth is 64 bit
normal build
SSE2 optimized codepath enabled
OpenMP support enabled
OpenCL support enabled
Lua support enabled, API version 5.0.2
Colord support disabled
gPhoto2 support enabled
GraphicsMagick support enabled
OpenEXR support enabled

The log file generated.
darktable-log.zip

Last few lines...
[sql] F:/msys64/home/chill/darktable/src/common/collection.c:834, function dt_collection_get(): prepare "SELECT id FROM main.selected_images AS s JOIN (SELECT DISTINCT mi.id FROM images AS mi WHERE (flags & 256) != 256 AND (1=1 AND (film_id IN (SELECT id FROM main.film_rolls WHERE folder LIKE 'F:\Temp\delete\Lumix\Kaas Plateau%'))) ORDER BY filename, filename , version) AS mi WHERE mi.id = s.imgid LIMIT -1, ?3" [dev_pixelpipe] took 0.000 secs (0.000 CPU) initing base buffer [thumbnail] 73.933686 [sql] F:/msys64/home/chill/darktable/src/common/tags.c:1589, function dt_tag_update_used_tags(): exec "INSERT OR IGNORE INTO main.used_tags (id, name) SELECT t.id, t.name FROM data.tags AS t, main.tagged_images AS i ON t.id = i.tagid GROUP BY t.id" 73.941688 [sql] F:/msys64/home/chill/darktable/src/common/exif.cc:2554, function dt_exif_xmp_read(): prepare "DELETE FROM main.masks_history WHERE imgid = ?1" 73.938685 [sql] F:/msys64/home/chill/darktable/src/common/collection.c:814, function dt_collection_get_selected_count(): prepare "SELECT COUNT(*) FROM main.selected_images" 73.942687 [sql] F:/msys64/home/chill/darktable/src/common/exif.cc:2610, function dt_exif_xmp_read(): prepare "DELETE FROM main.history WHERE imgid = ?1" 73.944686 [sql] F:/msys64/home/chill/darktable/src/views/lighttable.c:700, function _update_collected_images(): exec "DELETE FROM memory.collected_images" 73.945684 [sql] F:/msys64/home/chill/darktable/src/common/exif.cc:2624, function dt_exif_xmp_read(): prepare "INSERT INTO main.history (imgid, num, module, operation, op_params, enabled, blendop_params, blendop_version, multi_priority, multi_name, iop_order) VALUES (?1, ?2, ?3, ?4, ?5, ?6, ?7, ?8, ?9, ?10, ?11)" 73.946687 73.949683 [sql] F:/msys64/home/chill/darktable/src/common/exif.cc:2752, function dt_exif_xmp_read(): prepare "UPDATE main.images SET history_end = (SELECT IFNULL(MAX(num) + 1, 0) FROM main.history WHERE imgid = ?1) WHERE id = ?1" 73.946687 73.951684 [sql] F:/msys64/home/chill/darktable/src/common/exif.cc:2765, function dt_exif_xmp_read(): prepare "UPDATE main.images SET iop_order_version = ?1 WHERE id = ?2" [sql] F:/msys64/home/chill/darktable/src/views/lighttable.c:703, function _update_collected_images(): exec "DELETE FROM memory.sqlite_sequence WHERE name='colle

@jenshannoschwalm: you checked with windows? I think, it's a windows specific issue since my osx builds are working fine ...

it seems to be related to the generation of thumbnails in ~\AppData\Local\Microsoft\Windows\INetCache\darktable. If the mipmaps-... directory is deleted, darktable starts, but no new mipmaps-... directory is created.
also darktable-create-cache fails after processing the first file

I've the same issue with current master on windows.
I've tried with commit 580bf49da0f7527686a5978af37f9711a8067dd1. This one works for me.

I tested on linux only and i don't do any dt work/devel on windows. Thought that you ( @MStraeten ) were again testing on osx and that was really worrying me.

I've the same issue with current master on windows.
I've tried with commit 580bf49. This one works for me.

Thanks @phweyland , I built (darktable-2.7.0+1709~g580bf49da-win64) based on your commit referenced and it works

This same behaviour happened to me so not sure about a specific image being the issue on one of my recent installs I was prompted that my database needed updated and I selected yes. It seemed to work okay…sorry can’t remember what build but maybe around 1702?? My issue with this started when I tried to install 1727…I am compiling the latest version now and will see if the problem persists. I do know that in the past I update version right on top of one another without pursuing the install but I wondered if that was an issue so I use uninstall on my last couple of new installations so I am not sure if something happened there or not??

From: Hanno Schwalm notifications@github.com
Sent: September 19, 2019 1:30 AM
To: darktable-org/darktable darktable@noreply.github.com
Cc: Prior,Todd priort@mcmaster.ca; Comment comment@noreply.github.com
Subject: Re: [darktable-org/darktable] Current DT build on windows doesnt start app. (#2952)

I can see that your library.db contains signs of an old history. But on first sight i can't identify a database corruption.
You describe a situation where you import just one file to an empty database and can't use dt later onwards.
Could you share such an image file+xmp plus the config data as you sent right after that import?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/darktable-org/darktable/issues/2952?email_source=notifications&email_token=AKS2ES723YBXG3VTWLWJGMDQKME63A5CNFSM4IXOWK2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7CIIZY#issuecomment-532972647, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKS2ES72WCU2S642TBML2LTQKME63ANCNFSM4IXOWK2A.

i found 5ede285b9bedec8383ad9525f13ff9094548a16c beeing the commit introducing the termination.

i found 5ede285 beeing the commit introducing the termination.

It runs well until free(blob); but doesn't come back in mipmap_cache.c:
image

in memory.cpp:
#include <malloc.h> // for _aligned_malloc, _aligned_free

the windows version of dt_alloc_align() calls _aligned_malloc().

dt_malloc_align() => needs dt_free_align().

suggestion: dt_free_align() could encapsulate free() and _aligned_free() depending on the OS.
EDIT already done in darktable.h, see below.

image

image

@phweyland @MStraeten You guys are super sleuths...thanks for hunting this down.

Current build [darktable-2.7.0+1778~g57d00fa4c-win64.exe] with commit 57d00fa fixes the problem reported. Thank you all who were involved in resolving it.

My thanks as well..outside the scope of my talents by far so very grateful….

From: Murtuza Chhil notifications@github.com
Sent: September 20, 2019 3:45 AM
To: darktable-org/darktable darktable@noreply.github.com
Cc: Prior,Todd priort@mcmaster.ca; Comment comment@noreply.github.com
Subject: Re: [darktable-org/darktable] Current DT build on windows doesnt start app. (#2952)

Current build [darktable-2.7.0+1778~g57d00fa4c-win64.exe] with commit 57d00fahttps://github.com/darktable-org/darktable/commit/57d00fa4c21311821ced3afceaa48b9ce27eff30 fixes the problem reported. Thank you all who were involved in resolving it.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/darktable-org/darktable/issues/2952?email_source=notifications&email_token=AKS2ES3OBVWYPV22UVWIUBLQKR5PLA5CNFSM4IXOWK2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7F4ETY#issuecomment-533447247, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKS2ESZYZQRJKSKXISUTYP3QKR5PLANCNFSM4IXOWK2A.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

GrahamByrnes picture GrahamByrnes  Â·  3Comments

mjut picture mjut  Â·  5Comments

elstoc picture elstoc  Â·  4Comments

Nilvus picture Nilvus  Â·  5Comments

lovesegfault picture lovesegfault  Â·  3Comments