digiKam › digikam-users

digikam 5.1.0 start-up hanging on OSX

Classic

List

Threaded

24 messages Options

Pingu-Mann-Zɔro

digikam 5.1.0 start-up hanging on OSX

Hi all,

I'm a newbie on this list.

I installed a new version of digikam (was 4.1.0, now 5.1.0) on my OSX OS.
Starting for the first time, a pop-up message came which said "Scanning collections, please wait ..." and then "Preparing collection scan ...", where it hangs indefinitely.

Sometimes it just crashes at start-up.

Is there a problem with digikam 5.1.0 and OSX 10.11.6?

Regards,
PinguMann

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

typically no. It compiled with backward compatibility set to 10.8.

Here i tested with VM under older OSX version, and it do not crash or freeze.

Tip : create a new account and init digiKam with a fresh collection to see if problem is reproducible. Perhaps it's a problem with older 4.x settings (we have already a report about).

Gilles Caulier

2016-08-19 18:12 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

Hi all,

I'm a newbie on this list.

I installed a new version of digikam (was 4.1.0, now 5.1.0) on my OSX OS.
Starting for the first time, a pop-up message came which said "Scanning collections, please wait ..." and then "Preparing collection scan ...", where it hangs indefinitely.

Sometimes it just crashes at start-up.

Is there a problem with digikam 5.1.0 and OSX 10.11.6?

Regards,
PinguMann

diwi

Re: digikam 5.1.0 start-up hanging on OSX

I'm experiencing the same issue on a fresh 5.1.0 install on OS/X 10.11.6

First the collection is created by walking through the users Picture folder and then the digiKam boot screen/logo is displayed.

OS/X complains that the process hangs and after killing the process the following report header is created:
Date/Time: 2016-08-20 16:02:00 +0200
OS Version: Mac OS X 10.11.6 (Build 15G31)
Architecture: x86_64
Report Version: 22

Command: digikam
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Version: 5.1.0 (5.1.0)
Parent: launchd [1]
PID: 713

Event: hang
Duration: 1.10s (process was unresponsive for 98 seconds before sampling)
Steps: 11 (100ms sampling interval)

Regards Dirk

diwi

Re: digikam 5.1.0 start-up hanging on OSX

In reply to this post by Pingu-Mann-Zɔro

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

Well these information are not very suitable.

What do you see as debug traces when you start digiKam from a terminal ? Look here for more details :

https://www.digikam.org/contrib

Gilles Caulier

2016-08-20 16:10 GMT+02:00 Dirk Großkopf <[hidden email]>:

I'm experiencing the same issue on a fresh 5.1.0 install on OS/X 10.11.6

First the collection is created by walking through the users Picture folder and then the digiKam boot screen/logo is displayed.

OS/X complains that the process hangs and after killing the process the following report header is created:
Date/Time: 2016-08-20 16:02:00 +0200
OS Version: Mac OS X 10.11.6 (Build 15G31)
Architecture: x86_64
Report Version: 22

Command: digikam
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Version: 5.1.0 (5.1.0)
Parent: launchd [1]
PID: 713

Event: hang
Duration: 1.10s (process was unresponsive for 98 seconds before sampling)
Steps: 11 (100ms sampling interval)

Regards Dirk

diwi

Re: digikam 5.1.0 start-up hanging on OSX

I know

I was looking for some log files but didn’t found anythings

well Using the OS/X debugger does not provide any suitable, because the app launcher simply launches another process and exists doesn’t it.

Here’s the console output

mac-mini:~ dirkg$ lldb /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet

(lldb) target create "/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet"

Current executable set to '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64).

(lldb) run

Process 669 launched: '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64)

Process 669 exited with status = 0 (0x00000000)

to be more precise:

digiKam scans the defined/configured picture folder on startup and creates the database

Then the boot logo occurs and then stalls at step 3: Reading the database and waits forever

BTW: there is no executable digicam in /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/

Regards Dirk

Am 20.08.2016 um 21:06 schrieb Gilles Caulier <[hidden email]>:

Well these information are not very suitable.

What do you see as debug traces when you start digiKam from a terminal ? Look here for more details :

https://www.digikam.org/contrib

Gilles Caulier

2016-08-20 16:10 GMT+02:00 Dirk Großkopf <[hidden email]>:
I'm experiencing the same issue on a fresh 5.1.0 install on OS/X 10.11.6

First the collection is created by walking through the users Picture folder and then the digiKam boot screen/logo is displayed.

OS/X complains that the process hangs and after killing the process the following report header is created:
Date/Time: 2016-08-20 16:02:00 +0200
OS Version: Mac OS X 10.11.6 (Build 15G31)
Architecture: x86_64
Report Version: 22

Command: digikam
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Version: 5.1.0 (5.1.0)
Parent: launchd [1]
PID: 713

Event: hang
Duration: 1.10s (process was unresponsive for 98 seconds before sampling)
Steps: 11 (100ms sampling interval)

Regards Dirk

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

if you catch C++ exception before to run digiKam in lldb (as under gdb), it's not better to see where application hand ?

Gilles Caulier

2016-08-20 21:45 GMT+02:00 Dirk Großkopf <[hidden email]>:

I know
I was looking for some log files but didn’t found anythings
well Using the OS/X debugger does not provide any suitable, because the app launcher simply launches another process and exists doesn’t it.

Here’s the console output
mac-mini:~ dirkg$ lldb /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet

(lldb) target create "/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet"

Current executable set to '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64).
(lldb) run

Process 669 launched: '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64)

Process 669 exited with status = 0 (0x00000000)

to be more precise:
digiKam scans the defined/configured picture folder on startup and creates the database
Then the boot logo occurs and then stalls at step 3: Reading the database and waits forever

BTW: there is no executable digicam in /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/

Regards Dirk
Am 20.08.2016 um 21:06 schrieb Gilles Caulier <[hidden email]>:

Well these information are not very suitable.

What do you see as debug traces when you start digiKam from a terminal ? Look here for more details :

https://www.digikam.org/contrib

Gilles Caulier

2016-08-20 16:10 GMT+02:00 Dirk Großkopf <[hidden email]>:
I'm experiencing the same issue on a fresh 5.1.0 install on OS/X 10.11.6

First the collection is created by walking through the users Picture folder and then the digiKam boot screen/logo is displayed.

OS/X complains that the process hangs and after killing the process the following report header is created:
Date/Time: 2016-08-20 16:02:00 +0200
OS Version: Mac OS X 10.11.6 (Build 15G31)
Architecture: x86_64
Report Version: 22

Command: digikam
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Version: 5.1.0 (5.1.0)
Parent: launchd [1]
PID: 713

Event: hang
Duration: 1.10s (process was unresponsive for 98 seconds before sampling)
Steps: 11 (100ms sampling interval)

Regards Dirk

diwi

Re: digikam 5.1.0 start-up hanging on OSX

Hi Gilles

I tried to follow your suggestion to catch any exception in lldb, but failed. Anyway I was able to capture more details in the thread dump from the kill report:

Heaviest stack for the main thread of the target process:

11 start + 1 (libdyld.dylib + 13741) [0x7fff9c74a5ad]

11 main + 7343 (digikam + 72575) [0x10446db7f]

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 712625) [0x104526fb1]

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3377338) [0x1047b18ba]

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3379145) [0x1047b1fc9]

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3383314) [0x1047b3012]

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3378248) [0x1047b1c48]

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3497949) [0x1047cefdd]

11 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5]

4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d]

4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]

4 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf]

2 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494]

2 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8]

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110432) [0x105044f60]

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110757) [0x1050450a5]

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85]

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73660) [0x10503bfbc] (running)

Process: digikam [752]

Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam

Architecture: x86_64

Parent: launchd [1]

UID: 501

Task size: 57625 pages (+48)

CPU Time: 0.974s

Note: Unresponsive for 45 seconds before sampling

Thread 0xbced DispatchQueue 1 11 samples (1-11) priority 46 (base 46) cpu time 0.974s

11 start + 1 (libdyld.dylib + 13741) [0x7fff9c74a5ad] 1-11

11 main + 7343 (digikam + 72575) [0x10446db7f] 1-11

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 712625) [0x104526fb1] 1-11

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3377338) [0x1047b18ba] 1-11

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3379145) [0x1047b1fc9] 1-11

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3383314) [0x1047b3012] 1-11

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3378248) [0x1047b1c48] 1-11

11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3497949) [0x1047cefdd] 1-11

11 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 1-11

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3127715) [0x1047749a3] 1

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3047053) [0x104760e8d] 1

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3045541) [0x1047608a5] 1

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416825) [0x1047bb2f9] 1

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3436067) [0x1047bfe23] 1

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3485898) [0x1047cc0ca] 1

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 573237) [0x10b130f35] 1

1 malloc + 42 (libsystem_malloc.dylib + 4300) [0x7fff942780cc] 1

1 malloc_zone_malloc + 71 (libsystem_malloc.dylib + 9633) [0x7fff942795a1] 1

1 szone_malloc_should_clear + 292 (libsystem_malloc.dylib + 9989) [0x7fff94279705] 1

1 tiny_malloc_from_free_list + 484 (libsystem_malloc.dylib + 14496) [0x7fff9427a8a0] (running) 1

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7] 2-4

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3] 2-4

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35] 2-4

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a] 2-4

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d] 2-4

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5] 2-4

3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d] 2-4

3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4

3 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf] 2-4

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048088) [0x1054064d8] 2

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049741) [0x105406b4d] 2

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 866146) [0x10b178762] 2

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 574136) [0x10b1312b8] 2

1 szone_free_definite_size + 1278 (libsystem_malloc.dylib + 18556) [0x7fff9427b87c] (running) 2

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494] 3

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8] 3

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110432) [0x105044f60] 3

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110757) [0x1050450a5] 3

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85] 3

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73660) [0x10503bfbc] (running) 3

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048088) [0x1054064d8] 4

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049741) [0x105406b4d] 4

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 574049) [0x10b131261] (running) 4

2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 5-6

2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3279009) [0x1047998a1] 5-6

2 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1526803) [0x10b219c13] 5-6

2 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1525824) [0x10b219840] 5-6

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2829674) [0x10b357d6a] 5

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2831526) [0x10b3584a6] 5

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1174316) [0x10b1c3b2c] 5

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1168399) [0x10b1c240f] 5

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1170734) [0x10b1c2d2e] 5

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1636133) [0x10b234725] 5

1 readdir_r$INODE64 + 67 (libsystem_c.dylib + 184594) [0x7fffa041d112] 5

1 __getdirentries64 + 10 (libsystem_kernel.dylib + 91882) [0x7fff97c446ea] 5

*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 5

*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 5

*1 getdirentries64 + 55 (kernel + 3189799) [0xffffff800050ac27] 5

*1 ??? (kernel + 3236700) [0xffffff800051635c] 5

*1 vnode_readdir64 + 130 (kernel + 3188690) [0xffffff800050a7d2] 5

*1 hfs_vnop_readdir + 1333 (kernel + 5482837) [0xffffff800073a955] 5

*1 cat_getdirentries + 1111 (kernel + 5221063) [0xffffff80006faac7] 5

*1 BTIterateRecords + 1768 (kernel + 5525160) [0xffffff8000744ea8] 5

*1 GetBTreeBlock + 198 (kernel + 5192198) [0xffffff80006f3a06] 5

*1 buf_biowait + 124 (kernel + 3019132) [0xffffff80004e117c] 5

*1 ??? (kernel + 5988643) [0xffffff80007b6123] 5

*1 lck_mtx_sleep + 132 (kernel + 946676) [0xffffff80002e71f4] 5

*1 thread_block_reason + 175 (kernel + 986671) [0xffffff80002f0e2f] 5

*1 ??? (kernel + 1000220) [0xffffff80002f431c] 5

*1 machine_switch_context + 316 (kernel + 1875900) [0xffffff80003c9fbc] 5

1 stat$INODE64 + 10 (libsystem_kernel.dylib + 100178) [0x7fff97c46752] 6

*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 6

*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 6

*1 stat64 + 58 (kernel + 3180650) [0xffffff800050886a] 6

*1 ??? (kernel + 3224759) [0xffffff80005134b7] 6

*1 nameiat + 133 (kernel + 3169733) [0xffffff8000505dc5] 6

*1 namei + 2200 (kernel + 3090504) [0xffffff80004f2848] 6

*1 lookup + 910 (kernel + 3092638) [0xffffff80004f309e] 6

*1 hfs_vnop_lookup + 1517 (kernel + 5306925) [0xffffff800070fa2d] 6

*1 cat_lookup + 229 (kernel + 5200453) [0xffffff80006f5a45] 6

*1 bcopy + 22 (kernel + 18446744073708560534) [0xffffff800010e096] (running) 6

2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3127715) [0x1047749a3] 7-8

2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3047053) [0x104760e8d] 7-8

2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3045541) [0x1047608a5] 7-8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416866) [0x1047bb322] 7

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3342375) [0x1047a9027] 7

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3329312) [0x1047a5d20] (running) 7

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416803) [0x1047bb2e3] 8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3330608) [0x1047a6230] 8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 73341) [0x10448ae7d] 8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 76946) [0x10448bc92] 8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77058) [0x10448bd02] 8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77105) [0x10448bd31] 8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77326) [0x10448be0e] (running) 8

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 9

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3278948) [0x104799864] 9

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 181987) [0x1044a56e3] 9

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 862149) [0x10b1777c5] 9

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 803064) [0x10b1690f8] 9

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 777645) [0x10b162dad] (running) 9

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7] 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3] 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35] 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a] 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d] 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5] 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d] 10

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110587) [0x105044ffb] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 111332) [0x1050452e4] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76349) [0x10503ca3d] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76466) [0x10503cab2] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76521) [0x10503cae9] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85] 10

1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73721) [0x10503bff9] (running) 10

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 11

1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3279009) [0x1047998a1] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1526803) [0x10b219c13] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1525824) [0x10b219840] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2829674) [0x10b357d6a] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2831526) [0x10b3584a6] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1174316) [0x10b1c3b2c] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1168399) [0x10b1c240f] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1170734) [0x10b1c2d2e] 11

1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1636133) [0x10b234725] 11

1 readdir_r$INODE64 + 67 (libsystem_c.dylib + 184594) [0x7fffa041d112] 11

1 __getdirentries64 + 10 (libsystem_kernel.dylib + 91882) [0x7fff97c446ea] 11

*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 11

*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 11

*1 getdirentries64 + 55 (kernel + 3189799) [0xffffff800050ac27] 11

*1 ??? (kernel + 3236700) [0xffffff800051635c] 11

*1 vnode_readdir64 + 130 (kernel + 3188690) [0xffffff800050a7d2] 11

*1 hfs_vnop_readdir + 1333 (kernel + 5482837) [0xffffff800073a955] 11

*1 cat_getdirentries + 1111 (kernel + 5221063) [0xffffff80006faac7] 11

*1 BTIterateRecords + 1768 (kernel + 5525160) [0xffffff8000744ea8] 11

*1 GetBTreeBlock + 198 (kernel + 5192198) [0xffffff80006f3a06] 11

*1 buf_biowait + 124 (kernel + 3019132) [0xffffff80004e117c] 11

*1 ??? (kernel + 5988643) [0xffffff80007b6123] 11

*1 lck_mtx_sleep + 132 (kernel + 946676) [0xffffff80002e71f4] 11

*1 thread_block_reason + 175 (kernel + 986671) [0xffffff80002f0e2f] 11

*1 ??? (kernel + 1000220) [0xffffff80002f431c] 11

*1 machine_switch_context + 316 (kernel + 1875900) [0xffffff80003c9fbc] 11

Do you see any obvious?

Anyway I will try to follow your README file and build digikam from the sources next week and try to debug it since I have some 20+ years knowledge in software development, but didn’t used C++ for eons ;-)

Best Regards Dirk

Am 20.08.2016 um 22:19 schrieb Gilles Caulier <[hidden email]>:

if you catch C++ exception before to run digiKam in lldb (as under gdb), it's not better to see where application hand ?

Gilles Caulier

2016-08-20 21:45 GMT+02:00 Dirk Großkopf <[hidden email]>:
I know
I was looking for some log files but didn’t found anythings
well Using the OS/X debugger does not provide any suitable, because the app launcher simply launches another process and exists doesn’t it.

Here’s the console output
mac-mini:~ dirkg$ lldb /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet
(lldb) target create "/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet"

Current executable set to '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64).
(lldb) run
Process 669 launched: '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64)
Process 669 exited with status = 0 (0x00000000)

to be more precise:
digiKam scans the defined/configured picture folder on startup and creates the database
Then the boot logo occurs and then stalls at step 3: Reading the database and waits forever

BTW: there is no executable digicam in /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/

Regards Dirk
Am 20.08.2016 um 21:06 schrieb Gilles Caulier <[hidden email]>:

Well these information are not very suitable.

What do you see as debug traces when you start digiKam from a terminal ? Look here for more details :

https://www.digikam.org/contrib

Gilles Caulier

2016-08-20 16:10 GMT+02:00 Dirk Großkopf <[hidden email]>:
I'm experiencing the same issue on a fresh 5.1.0 install on OS/X 10.11.6

First the collection is created by walking through the users Picture folder and then the digiKam boot screen/logo is displayed.

OS/X complains that the process hangs and after killing the process the following report header is created:
Date/Time: 2016-08-20 16:02:00 +0200
OS Version: Mac OS X 10.11.6 (Build 15G31)
Architecture: x86_64
Report Version: 22

Command: digikam
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Version: 5.1.0 (5.1.0)
Parent: launchd [1]
PID: 713

Event: hang
Duration: 1.10s (process was unresponsive for 98 seconds before sampling)
Steps: 11 (100ms sampling interval)

Regards Dirk

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

Not really suitable.

It talk about memory allocation and HFS partition access. But for the rest, it's really not readable...

I remember some problem with Qt4 and OSX about amount files to open at the same time which can break application at runtime. Perhaps this also valide with Qt5, but since I packaging for OSX very quickly with 5.X release, I never seen this problem.

http://superuser.com/questions/433746/is-there-a-fix-for-the-too-many-open-files-in-system-error-on-os-x-10-7-1

I can build 5.2.0 beta PKG if you want to test with current implementation.

Gilles Caulier

2016-08-21 17:28 GMT+02:00 Dirk Großkopf <[hidden email]>:

Hi Gilles

I tried to follow your suggestion to catch any exception in lldb, but failed. Anyway I was able to capture more details in the thread dump from the kill report:

Heaviest stack for the main thread of the target process:
11 start + 1 (libdyld.dylib + 13741) [0x7fff9c74a5ad]
11 main + 7343 (digikam + 72575) [0x10446db7f]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 712625) [0x104526fb1]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3377338) [0x1047b18ba]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3379145) [0x1047b1fc9]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3383314) [0x1047b3012]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3378248) [0x1047b1c48]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3497949) [0x1047cefdd]
11 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf]
2 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494]
2 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110432) [0x105044f60]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110757) [0x1050450a5]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73660) [0x10503bfbc] (running)

Process: digikam [752]
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Architecture: x86_64
Parent: launchd [1]
UID: 501
Task size: 57625 pages (+48)
CPU Time: 0.974s
Note: Unresponsive for 45 seconds before sampling

Thread 0xbced DispatchQueue 1 11 samples (1-11) priority 46 (base 46) cpu time 0.974s
<thread QoS user interactive (requested user interactive), process unclamped, process received importance donation from WindowServer [262], IO policy important>
11 start + 1 (libdyld.dylib + 13741) [0x7fff9c74a5ad] 1-11
11 main + 7343 (digikam + 72575) [0x10446db7f] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 712625) [0x104526fb1] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3377338) [0x1047b18ba] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3379145) [0x1047b1fc9] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3383314) [0x1047b3012] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3378248) [0x1047b1c48] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3497949) [0x1047cefdd] 1-11
11 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 1-11
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3127715) [0x1047749a3] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3047053) [0x104760e8d] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3045541) [0x1047608a5] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416825) [0x1047bb2f9] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3436067) [0x1047bfe23] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3485898) [0x1047cc0ca] 1
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 573237) [0x10b130f35] 1
1 malloc + 42 (libsystem_malloc.dylib + 4300) [0x7fff942780cc] 1
1 malloc_zone_malloc + 71 (libsystem_malloc.dylib + 9633) [0x7fff942795a1] 1
1 szone_malloc_should_clear + 292 (libsystem_malloc.dylib + 9989) [0x7fff94279705] 1
1 tiny_malloc_from_free_list + 484 (libsystem_malloc.dylib + 14496) [0x7fff9427a8a0] (running) 1
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4
3 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf] 2-4
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048088) [0x1054064d8] 2
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049741) [0x105406b4d] 2
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 866146) [0x10b178762] 2
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 574136) [0x10b1312b8] 2
1 szone_free_definite_size + 1278 (libsystem_malloc.dylib + 18556) [0x7fff9427b87c] (running) 2
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110432) [0x105044f60] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110757) [0x1050450a5] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73660) [0x10503bfbc] (running) 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048088) [0x1054064d8] 4
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049741) [0x105406b4d] 4
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 574049) [0x10b131261] (running) 4
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 5-6
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3279009) [0x1047998a1] 5-6
2 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1526803) [0x10b219c13] 5-6
2 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1525824) [0x10b219840] 5-6
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2829674) [0x10b357d6a] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2831526) [0x10b3584a6] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1174316) [0x10b1c3b2c] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1168399) [0x10b1c240f] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1170734) [0x10b1c2d2e] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1636133) [0x10b234725] 5
1 readdir_r$INODE64 + 67 (libsystem_c.dylib + 184594) [0x7fffa041d112] 5
1 __getdirentries64 + 10 (libsystem_kernel.dylib + 91882) [0x7fff97c446ea] 5
*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 5
*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 5
*1 getdirentries64 + 55 (kernel + 3189799) [0xffffff800050ac27] 5
*1 ??? (kernel + 3236700) [0xffffff800051635c] 5
*1 vnode_readdir64 + 130 (kernel + 3188690) [0xffffff800050a7d2] 5
*1 hfs_vnop_readdir + 1333 (kernel + 5482837) [0xffffff800073a955] 5
*1 cat_getdirentries + 1111 (kernel + 5221063) [0xffffff80006faac7] 5
*1 BTIterateRecords + 1768 (kernel + 5525160) [0xffffff8000744ea8] 5
*1 GetBTreeBlock + 198 (kernel + 5192198) [0xffffff80006f3a06] 5
*1 buf_biowait + 124 (kernel + 3019132) [0xffffff80004e117c] 5
*1 ??? (kernel + 5988643) [0xffffff80007b6123] 5
*1 lck_mtx_sleep + 132 (kernel + 946676) [0xffffff80002e71f4] 5
*1 thread_block_reason + 175 (kernel + 986671) [0xffffff80002f0e2f] 5
*1 ??? (kernel + 1000220) [0xffffff80002f431c] 5
*1 machine_switch_context + 316 (kernel + 1875900) [0xffffff80003c9fbc] 5
1 stat$INODE64 + 10 (libsystem_kernel.dylib + 100178) [0x7fff97c46752] 6
*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 6
*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 6
*1 stat64 + 58 (kernel + 3180650) [0xffffff800050886a] 6
*1 ??? (kernel + 3224759) [0xffffff80005134b7] 6
*1 nameiat + 133 (kernel + 3169733) [0xffffff8000505dc5] 6
*1 namei + 2200 (kernel + 3090504) [0xffffff80004f2848] 6
*1 lookup + 910 (kernel + 3092638) [0xffffff80004f309e] 6
*1 hfs_vnop_lookup + 1517 (kernel + 5306925) [0xffffff800070fa2d] 6
*1 cat_lookup + 229 (kernel + 5200453) [0xffffff80006f5a45] 6
*1 bcopy + 22 (kernel + 18446744073708560534) [0xffffff800010e096] (running) 6
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3127715) [0x1047749a3] 7-8
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3047053) [0x104760e8d] 7-8
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3045541) [0x1047608a5] 7-8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416866) [0x1047bb322] 7
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3342375) [0x1047a9027] 7
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3329312) [0x1047a5d20] (running) 7
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416803) [0x1047bb2e3] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3330608) [0x1047a6230] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 73341) [0x10448ae7d] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 76946) [0x10448bc92] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77058) [0x10448bd02] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77105) [0x10448bd31] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77326) [0x10448be0e] (running) 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 9
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3278948) [0x104799864] 9
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 181987) [0x1044a56e3] 9
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 862149) [0x10b1777c5] 9
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 803064) [0x10b1690f8] 9
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 777645) [0x10b162dad] (running) 9
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110587) [0x105044ffb] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 111332) [0x1050452e4] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76349) [0x10503ca3d] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76466) [0x10503cab2] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76521) [0x10503cae9] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73721) [0x10503bff9] (running) 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 11
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3279009) [0x1047998a1] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1526803) [0x10b219c13] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1525824) [0x10b219840] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2829674) [0x10b357d6a] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2831526) [0x10b3584a6] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1174316) [0x10b1c3b2c] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1168399) [0x10b1c240f] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1170734) [0x10b1c2d2e] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1636133) [0x10b234725] 11
1 readdir_r$INODE64 + 67 (libsystem_c.dylib + 184594) [0x7fffa041d112] 11
1 __getdirentries64 + 10 (libsystem_kernel.dylib + 91882) [0x7fff97c446ea] 11
*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 11
*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 11
*1 getdirentries64 + 55 (kernel + 3189799) [0xffffff800050ac27] 11
*1 ??? (kernel + 3236700) [0xffffff800051635c] 11
*1 vnode_readdir64 + 130 (kernel + 3188690) [0xffffff800050a7d2] 11
*1 hfs_vnop_readdir + 1333 (kernel + 5482837) [0xffffff800073a955] 11
*1 cat_getdirentries + 1111 (kernel + 5221063) [0xffffff80006faac7] 11
*1 BTIterateRecords + 1768 (kernel + 5525160) [0xffffff8000744ea8] 11
*1 GetBTreeBlock + 198 (kernel + 5192198) [0xffffff80006f3a06] 11
*1 buf_biowait + 124 (kernel + 3019132) [0xffffff80004e117c] 11
*1 ??? (kernel + 5988643) [0xffffff80007b6123] 11
*1 lck_mtx_sleep + 132 (kernel + 946676) [0xffffff80002e71f4] 11
*1 thread_block_reason + 175 (kernel + 986671) [0xffffff80002f0e2f] 11
*1 ??? (kernel + 1000220) [0xffffff80002f431c] 11
*1 machine_switch_context + 316 (kernel + 1875900) [0xffffff80003c9fbc] 11

Do you see any obvious?
Anyway I will try to follow your README file and build digikam from the sources next week and try to debug it since I have some 20+ years knowledge in software development, but didn’t used C++ for eons ;-)

Best Regards Dirk

Am 20.08.2016 um 22:19 schrieb Gilles Caulier <[hidden email]>:

if you catch C++ exception before to run digiKam in lldb (as under gdb), it's not better to see where application hand ?

Gilles Caulier

2016-08-20 21:45 GMT+02:00 Dirk Großkopf <[hidden email]>:
I know
I was looking for some log files but didn’t found anythings
well Using the OS/X debugger does not provide any suitable, because the app launcher simply launches another process and exists doesn’t it.

Here’s the console output
mac-mini:~ dirkg$ lldb /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet
(lldb) target create "/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet"

Current executable set to '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64).
(lldb) run
Process 669 launched: '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64)
Process 669 exited with status = 0 (0x00000000)

to be more precise:
digiKam scans the defined/configured picture folder on startup and creates the database
Then the boot logo occurs and then stalls at step 3: Reading the database and waits forever

BTW: there is no executable digicam in /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/

Regards Dirk
Am 20.08.2016 um 21:06 schrieb Gilles Caulier <[hidden email]>:

Well these information are not very suitable.

What do you see as debug traces when you start digiKam from a terminal ? Look here for more details :

https://www.digikam.org/contrib

Gilles Caulier

2016-08-20 16:10 GMT+02:00 Dirk Großkopf <[hidden email]>:
I'm experiencing the same issue on a fresh 5.1.0 install on OS/X 10.11.6

First the collection is created by walking through the users Picture folder and then the digiKam boot screen/logo is displayed.

OS/X complains that the process hangs and after killing the process the following report header is created:
Date/Time: 2016-08-20 16:02:00 +0200
OS Version: Mac OS X 10.11.6 (Build 15G31)
Architecture: x86_64
Report Version: 22

Command: digikam
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Version: 5.1.0 (5.1.0)
Parent: launchd [1]
PID: 713

Event: hang
Duration: 1.10s (process was unresponsive for 98 seconds before sampling)
Steps: 11 (100ms sampling interval)

Regards Dirk

Pingu-Mann-Zɔro

Re: digikam 5.1.0 start-up hanging on OSX

In reply to this post by Gilles Caulier-4

Thanks for the tip Gilles,

I started an install in a new User account. It has been running now for about 6 hours with the "Scanning collections ....". I've about 200GB of photos. How long should a new installation (fresh collection) take with default options in the installation?

System:
Processor Name:   Intel Core i7
Processor Speed:   2,3 GHz
Number of Processors:   1
Total Number of Cores:   4
L2 Cache (per Core):   256 KB
L3 Cache:   6 MB
Memory:   16 GB
Disks:
OS SSD: Samsung SSD 840 EVO 750GB:
Data HDD: ST2000LM003 HN-M201RAD

BR

On 20160819 19:19, Gilles Caulier wrote:

typically no. It compiled with backward compatibility set to 10.8.

Here i tested with VM under older OSX version, and it do not crash or freeze.

Tip : create a new account and init digiKam with a fresh collection to see if problem is reproducible. Perhaps it's a problem with older 4.x settings (we have already a report about).

Gilles Caulier

2016-08-19 18:12 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

Hi all,

I'm a newbie on this list.

I installed a new version of digikam (was 4.1.0, now 5.1.0) on my OSX OS.
Starting for the first time, a pop-up message came which said "Scanning collections, please wait ..." and then "Preparing collection scan ...", where it hangs indefinitely.

Sometimes it just crashes at start-up.

Is there a problem with digikam 5.1.0 and OSX 10.11.6?

Regards,
PinguMann

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

The scanning collection register album on database. It can take a while but i suspect that data HDD is USB one. right ?

If yes, it a really slow solution. The best : USB3 minimum + SSD, not HDD.

Here, i use 1Tb SSD to howst all my collection (250Gb) and it take 30 mn to scan all albums.

Database is sqlite.

Gilles Caulier

2016-08-24 13:50 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

Thanks for the tip Gilles,

I started an install in a new User account. It has been running now for about 6 hours with the "Scanning collections ....". I've about 200GB of photos. How long should a new installation (fresh collection) take with default options in the installation?

System:
Processor Name:   Intel Core i7
Processor Speed:   2,3 GHz
Number of Processors:   1
Total Number of Cores:   4
L2 Cache (per Core):   256 KB
L3 Cache:   6 MB
Memory:   16 GB
Disks:
OS SSD: Samsung SSD 840 EVO 750GB:
Data HDD: ST2000LM003 HN-M201RAD

BR

On 20160819 19:19, Gilles Caulier wrote:

typically no. It compiled with backward compatibility set to 10.8.

Here i tested with VM under older OSX version, and it do not crash or freeze.

Tip : create a new account and init digiKam with a fresh collection to see if problem is reproducible. Perhaps it's a problem with older 4.x settings (we have already a report about).

Gilles Caulier

2016-08-19 18:12 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

Hi all,

I'm a newbie on this list.

I installed a new version of digikam (was 4.1.0, now 5.1.0) on my OSX OS.
Starting for the first time, a pop-up message came which said "Scanning collections, please wait ..." and then "Preparing collection scan ...", where it hangs indefinitely.

Sometimes it just crashes at start-up.

Is there a problem with digikam 5.1.0 and OSX 10.11.6?

Regards,
PinguMann

Pingu-Mann-Zɔro

Re: digikam 5.1.0 start-up hanging on OSX

No. the HDD is in the DVD Bay, connected to the SATAIII bus. It has the same bus as the SSD. The older Intel-Macs (Jobs-Era) only have USB2, so USB2 attached Drives are a pain in the A. I now use a BlueRay-DVD over the USB2, in the rather few times I need it these days.

I keep Data separate from OS for obvious reasons, and removed the less needed DVD.

The only possible issue can perhaps be that the Data on the HDD is soft linked in the /Users/User-Name/Pictures directory to standard the "Pictures" directory of the OSX system. It has worked very well without any issues with all OSX 8-10 versions till now.

I heard that sqlite is rather lite-wheight in speed. Anyone tried a MySQL set-up locally on a MBP? Any experiences in the group will be a great help? I will try a local OSX MySQL server on my Laptop first, then migrate it later to a self hosted Server.

BR,

On 20160824 15:24, Gilles Caulier wrote:

The scanning collection register album on database. It can take a while but i suspect that data HDD is USB one. right ?

If yes, it a really slow solution. The best : USB3 minimum + SSD, not HDD.

Here, i use 1Tb SSD to howst all my collection (250Gb) and it take 30 mn to scan all albums.

Database is sqlite.

Gilles Caulier

2016-08-24 13:50 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

Thanks for the tip Gilles,

I started an install in a new User account. It has been running now for about 6 hours with the "Scanning collections ....". I've about 200GB of photos. How long should a new installation (fresh collection) take with default options in the installation?

System:
Processor Name:   Intel Core i7
Processor Speed:   2,3 GHz
Number of Processors:   1
Total Number of Cores:   4
L2 Cache (per Core):   256 KB
L3 Cache:   6 MB
Memory:   16 GB
Disks:
OS SSD: Samsung SSD 840 EVO 750GB:
Data HDD: ST2000LM003 HN-M201RAD

BR

On 20160819 19:19, Gilles Caulier wrote:

typically no. It compiled with backward compatibility set to 10.8.

Here i tested with VM under older OSX version, and it do not crash or freeze.

Tip : create a new account and init digiKam with a fresh collection to see if problem is reproducible. Perhaps it's a problem with older 4.x settings (we have already a report about).

Gilles Caulier

2016-08-19 18:12 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

Hi all,

I'm a newbie on this list.

I installed a new version of digikam (was 4.1.0, now 5.1.0) on my OSX OS.
Starting for the first time, a pop-up message came which said "Scanning collections, please wait ..." and then "Preparing collection scan ...", where it hangs indefinitely.

Sometimes it just crashes at start-up.

Is there a problem with digikam 5.1.0 and OSX 10.11.6?

Regards,
PinguMann

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

2016-08-24 18:58 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

No. the HDD is in the DVD Bay, connected to the SATAIII bus. It has the same bus as the SSD. The older Intel-Macs (Jobs-Era) only have USB2, so USB2 attached Drives are a pain in the A. I now use a BlueRay-DVD over the USB2, in the rather few times I need it these days.

I keep Data separate from OS for obvious reasons, and removed the less needed DVD.

The only possible issue can perhaps be that the Data on the HDD is soft linked in the /Users/User-Name/Pictures directory to standard the "Pictures" directory of the OSX system. It has worked very well without any issues with all OSX 8-10 versions till now.

I heard that sqlite is rather lite-wheight in speed. Anyone tried a MySQL set-up locally on a MBP?

Me on my macbook pro. The server was installed on configured in my Linux desktop for testing. It work, but take a care that wiki connection will slow down digiKam. Using ethernet give better results.

Gilles Caulier

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

Please see bug 367853

I also shared a new fresh PKG installer in this entry, if you is interested.

Gilles Caulier

2016-08-25 9:29 GMT+02:00 Gilles Caulier <[hidden email]>:

2016-08-24 18:58 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

No. the HDD is in the DVD Bay, connected to the SATAIII bus. It has the same bus as the SSD. The older Intel-Macs (Jobs-Era) only have USB2, so USB2 attached Drives are a pain in the A. I now use a BlueRay-DVD over the USB2, in the rather few times I need it these days.

I keep Data separate from OS for obvious reasons, and removed the less needed DVD.

The only possible issue can perhaps be that the Data on the HDD is soft linked in the /Users/User-Name/Pictures directory to standard the "Pictures" directory of the OSX system. It has worked very well without any issues with all OSX 8-10 versions till now.

I heard that sqlite is rather lite-wheight in speed. Anyone tried a MySQL set-up locally on a MBP?

Me on my macbook pro. The server was installed on configured in my Linux desktop for testing. It work, but take a care that wiki connection will slow down digiKam. Using ethernet give better results.

Gilles Caulier

diwi

Re: digikam 5.1.0 start-up hanging on OSX

In reply to this post by diwi

Hi Gilles

I was able to track down the root cause: Database Access is slow

So here's what I did:
- removed the digicamrc configuration
- linked only one subfolder with ~2000 pictures
->digicam started, displayed empty preview pane and it took 5 minutes to load the metadata.

So false alert: No crash or deadlock, but poor performance

Best Regards

Dirk

Am 21.08.2016 um 17:28 schrieb Dirk Großkopf <[hidden email]>:

Hi Gilles

I tried to follow your suggestion to catch any exception in lldb, but failed. Anyway I was able to capture more details in the thread dump from the kill report:

Heaviest stack for the main thread of the target process:
11 start + 1 (libdyld.dylib + 13741) [0x7fff9c74a5ad]
11 main + 7343 (digikam + 72575) [0x10446db7f]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 712625) [0x104526fb1]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3377338) [0x1047b18ba]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3379145) [0x1047b1fc9]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3383314) [0x1047b3012]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3378248) [0x1047b1c48]
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3497949) [0x1047cefdd]
11 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5]
4 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d]
4 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796]
4 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf]
2 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494]
2 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110432) [0x105044f60]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110757) [0x1050450a5]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85]
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73660) [0x10503bfbc] (running)

Process: digikam [752]
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Architecture: x86_64
Parent: launchd [1]
UID: 501
Task size: 57625 pages (+48)
CPU Time: 0.974s
Note: Unresponsive for 45 seconds before sampling

Thread 0xbced DispatchQueue 1 11 samples (1-11) priority 46 (base 46) cpu time 0.974s
<thread QoS user interactive (requested user interactive), process unclamped, process received importance donation from WindowServer [262], IO policy important>
11 start + 1 (libdyld.dylib + 13741) [0x7fff9c74a5ad] 1-11
11 main + 7343 (digikam + 72575) [0x10446db7f] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 712625) [0x104526fb1] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3377338) [0x1047b18ba] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3379145) [0x1047b1fc9] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3383314) [0x1047b3012] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3378248) [0x1047b1c48] 1-11
11 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3497949) [0x1047cefdd] 1-11
11 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 1-11
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3127715) [0x1047749a3] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3047053) [0x104760e8d] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3045541) [0x1047608a5] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416825) [0x1047bb2f9] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3436067) [0x1047bfe23] 1
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3485898) [0x1047cc0ca] 1
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 573237) [0x10b130f35] 1
1 malloc + 42 (libsystem_malloc.dylib + 4300) [0x7fff942780cc] 1
1 malloc_zone_malloc + 71 (libsystem_malloc.dylib + 9633) [0x7fff942795a1] 1
1 szone_malloc_should_clear + 292 (libsystem_malloc.dylib + 9989) [0x7fff94279705] 1
1 tiny_malloc_from_free_list + 484 (libsystem_malloc.dylib + 14496) [0x7fff9427a8a0] (running) 1
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5] 2-4
3 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d] 2-4
3 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 2-4
3 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf] 2-4
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048088) [0x1054064d8] 2
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049741) [0x105406b4d] 2
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 866146) [0x10b178762] 2
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 574136) [0x10b1312b8] 2
1 szone_free_definite_size + 1278 (libsystem_malloc.dylib + 18556) [0x7fff9427b87c] (running) 2
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110432) [0x105044f60] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110757) [0x1050450a5] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85] 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73660) [0x10503bfbc] (running) 3
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048088) [0x1054064d8] 4
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049741) [0x105406b4d] 4
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 574049) [0x10b131261] (running) 4
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 5-6
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3279009) [0x1047998a1] 5-6
2 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1526803) [0x10b219c13] 5-6
2 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1525824) [0x10b219840] 5-6
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2829674) [0x10b357d6a] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2831526) [0x10b3584a6] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1174316) [0x10b1c3b2c] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1168399) [0x10b1c240f] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1170734) [0x10b1c2d2e] 5
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1636133) [0x10b234725] 5
1 readdir_r$INODE64 + 67 (libsystem_c.dylib + 184594) [0x7fffa041d112] 5
1 __getdirentries64 + 10 (libsystem_kernel.dylib + 91882) [0x7fff97c446ea] 5
*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 5
*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 5
*1 getdirentries64 + 55 (kernel + 3189799) [0xffffff800050ac27] 5
*1 ??? (kernel + 3236700) [0xffffff800051635c] 5
*1 vnode_readdir64 + 130 (kernel + 3188690) [0xffffff800050a7d2] 5
*1 hfs_vnop_readdir + 1333 (kernel + 5482837) [0xffffff800073a955] 5
*1 cat_getdirentries + 1111 (kernel + 5221063) [0xffffff80006faac7] 5
*1 BTIterateRecords + 1768 (kernel + 5525160) [0xffffff8000744ea8] 5
*1 GetBTreeBlock + 198 (kernel + 5192198) [0xffffff80006f3a06] 5
*1 buf_biowait + 124 (kernel + 3019132) [0xffffff80004e117c] 5
*1 ??? (kernel + 5988643) [0xffffff80007b6123] 5
*1 lck_mtx_sleep + 132 (kernel + 946676) [0xffffff80002e71f4] 5
*1 thread_block_reason + 175 (kernel + 986671) [0xffffff80002f0e2f] 5
*1 ??? (kernel + 1000220) [0xffffff80002f431c] 5
*1 machine_switch_context + 316 (kernel + 1875900) [0xffffff80003c9fbc] 5
1 stat$INODE64 + 10 (libsystem_kernel.dylib + 100178) [0x7fff97c46752] 6
*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 6
*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 6
*1 stat64 + 58 (kernel + 3180650) [0xffffff800050886a] 6
*1 ??? (kernel + 3224759) [0xffffff80005134b7] 6
*1 nameiat + 133 (kernel + 3169733) [0xffffff8000505dc5] 6
*1 namei + 2200 (kernel + 3090504) [0xffffff80004f2848] 6
*1 lookup + 910 (kernel + 3092638) [0xffffff80004f309e] 6
*1 hfs_vnop_lookup + 1517 (kernel + 5306925) [0xffffff800070fa2d] 6
*1 cat_lookup + 229 (kernel + 5200453) [0xffffff80006f5a45] 6
*1 bcopy + 22 (kernel + 18446744073708560534) [0xffffff800010e096] (running) 6
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3127715) [0x1047749a3] 7-8
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3047053) [0x104760e8d] 7-8
2 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3045541) [0x1047608a5] 7-8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416866) [0x1047bb322] 7
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3342375) [0x1047a9027] 7
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3329312) [0x1047a5d20] (running) 7
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3416803) [0x1047bb2e3] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3330608) [0x1047a6230] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 73341) [0x10448ae7d] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 76946) [0x10448bc92] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77058) [0x10448bd02] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77105) [0x10448bd31] 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 77326) [0x10448be0e] (running) 8
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 9
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3278948) [0x104799864] 9
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 181987) [0x1044a56e3] 9
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 862149) [0x10b1777c5] 9
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 803064) [0x10b1690f8] 9
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 777645) [0x10b162dad] (running) 9
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3118263) [0x1047724b7] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3055469) [0x104762f6d] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1858819) [0x10b26ad03] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1825542) [0x10b262b06] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1822902) [0x10b2620b6] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1701696) [0x10b244740] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885774) [0x10b36588e] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3254947) [0x104793aa3] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251765) [0x104792e35] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251306) [0x104792c6a] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3251613) [0x104792d9d] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3059109) [0x104763da5] 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3058913) [0x104763ce1] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2885277) [0x10b36569d] 10
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2267030) [0x10b2ce796] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4759519) [0x1054b3fdf] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4048020) [0x105406494] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 4049608) [0x105406ac8] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 110587) [0x105044ffb] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 111332) [0x1050452e4] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76349) [0x10503ca3d] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76466) [0x10503cab2] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 76521) [0x10503cae9] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73605) [0x10503bf85] 10
1 ??? (<AF1B03E4-C08D-3649-9482-E742EEDB523B> + 73721) [0x10503bff9] (running) 10
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3515607) [0x1047d34d7] 11
1 ??? (<44130343-5D3B-3BC4-B853-00AE122DA68D> + 3279009) [0x1047998a1] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1526803) [0x10b219c13] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1525824) [0x10b219840] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2829674) [0x10b357d6a] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 2831526) [0x10b3584a6] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1174316) [0x10b1c3b2c] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1168399) [0x10b1c240f] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1170734) [0x10b1c2d2e] 11
1 ??? (<92CAC82F-5CA4-35B1-A4BF-78268E053E4B> + 1636133) [0x10b234725] 11
1 readdir_r$INODE64 + 67 (libsystem_c.dylib + 184594) [0x7fffa041d112] 11
1 __getdirentries64 + 10 (libsystem_kernel.dylib + 91882) [0x7fff97c446ea] 11
*1 hndl_unix_scall64 + 22 (kernel + 2018662) [0xffffff80003ecd66] 11
*1 unix_syscall64 + 593 (kernel + 6457089) [0xffffff8000828701] 11
*1 getdirentries64 + 55 (kernel + 3189799) [0xffffff800050ac27] 11
*1 ??? (kernel + 3236700) [0xffffff800051635c] 11
*1 vnode_readdir64 + 130 (kernel + 3188690) [0xffffff800050a7d2] 11
*1 hfs_vnop_readdir + 1333 (kernel + 5482837) [0xffffff800073a955] 11
*1 cat_getdirentries + 1111 (kernel + 5221063) [0xffffff80006faac7] 11
*1 BTIterateRecords + 1768 (kernel + 5525160) [0xffffff8000744ea8] 11
*1 GetBTreeBlock + 198 (kernel + 5192198) [0xffffff80006f3a06] 11
*1 buf_biowait + 124 (kernel + 3019132) [0xffffff80004e117c] 11
*1 ??? (kernel + 5988643) [0xffffff80007b6123] 11
*1 lck_mtx_sleep + 132 (kernel + 946676) [0xffffff80002e71f4] 11
*1 thread_block_reason + 175 (kernel + 986671) [0xffffff80002f0e2f] 11
*1 ??? (kernel + 1000220) [0xffffff80002f431c] 11
*1 machine_switch_context + 316 (kernel + 1875900) [0xffffff80003c9fbc] 11

Do you see any obvious?
Anyway I will try to follow your README file and build digikam from the sources next week and try to debug it since I have some 20+ years knowledge in software development, but didn’t used C++ for eons ;-)

Best Regards Dirk

Am 20.08.2016 um 22:19 schrieb Gilles Caulier <[hidden email]>:

if you catch C++ exception before to run digiKam in lldb (as under gdb), it's not better to see where application hand ?

Gilles Caulier

2016-08-20 21:45 GMT+02:00 Dirk Großkopf <[hidden email]>:
I know
I was looking for some log files but didn’t found anythings
well Using the OS/X debugger does not provide any suitable, because the app launcher simply launches another process and exists doesn’t it.

Here’s the console output
mac-mini:~ dirkg$ lldb /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet
(lldb) target create "/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet"

Current executable set to '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64).
(lldb) run
Process 669 launched: '/opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/applet' (x86_64)
Process 669 exited with status = 0 (0x00000000)

to be more precise:
digiKam scans the defined/configured picture folder on startup and creates the database
Then the boot logo occurs and then stalls at step 3: Reading the database and waits forever

BTW: there is no executable digicam in /opt/digikam/Applications/digiKam/digikam.app/Contents/MacOS/

Regards Dirk
Am 20.08.2016 um 21:06 schrieb Gilles Caulier <[hidden email]>:

Well these information are not very suitable.

What do you see as debug traces when you start digiKam from a terminal ? Look here for more details :

https://www.digikam.org/contrib

Gilles Caulier

2016-08-20 16:10 GMT+02:00 Dirk Großkopf <[hidden email]>:
I'm experiencing the same issue on a fresh 5.1.0 install on OS/X 10.11.6

First the collection is created by walking through the users Picture folder and then the digiKam boot screen/logo is displayed.

OS/X complains that the process hangs and after killing the process the following report header is created:
Date/Time: 2016-08-20 16:02:00 +0200
OS Version: Mac OS X 10.11.6 (Build 15G31)
Architecture: x86_64
Report Version: 22

Command: digikam
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Version: 5.1.0 (5.1.0)
Parent: launchd [1]
PID: 713

Event: hang
Duration: 1.10s (process was unresponsive for 98 seconds before sampling)
Steps: 11 (100ms sampling interval)

Regards Dirk

Pingu-Mann-Zɔro

Re: digikam 5.1.0 start-up hanging on OSX

In reply to this post by Gilles Caulier-4

Hi all,

after not being able to carry on further with this issue, I returned again today and installed DK 3.5.0.

The reading of the collections problem and bug 367853 is still a problem.

@Gilles Caulier, I tried to download your suggested installer:
"I also shared a new fresh PKG installer in this entry, if you is interested." Unfortunately The link is dead now.

Andrea: https://bugs.kde.org/show_bug.cgi?id=367853#c4 also reports to have tried it, without result.

Any new info on the issue?

System now:
DigiKam 5.3.0
MacOS Sierra, SSD & HDD on SATAIII bus.
Photos & iPhoto were not used, negating large db problems with them.
Attachment of Hangup screen -- It remains there for hours (tested up to 6):

__________
Process:               digikam [44928]
Path:                  /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier:            digikam
Version:               5.3.0 (5.3.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           digikam [44928]
User ID:               501
OS Version:            Mac OS X 10.12.2 (16C67)
___________

Regards,

On 27/08/2016 10:42, Gilles Caulier wrote:

Please see bug 367853

I also shared a new fresh PKG installer in this entry, if you is interested.

Gilles Caulier

2016-08-25 9:29 GMT+02:00 Gilles Caulier <[hidden email]>:

2016-08-24 18:58 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

No. the HDD is in the DVD Bay, connected to the SATAIII bus. It has the same bus as the SSD. The older Intel-Macs (Jobs-Era) only have USB2, so USB2 attached Drives are a pain in the A. I now use a BlueRay-DVD over the USB2, in the rather few times I need it these days.

I keep Data separate from OS for obvious reasons, and removed the less needed DVD.

The only possible issue can perhaps be that the Data on the HDD is soft linked in the /Users/User-Name/Pictures directory to standard the "Pictures" directory of the OSX system. It has worked very well without any issues with all OSX 8-10 versions till now.

I heard that sqlite is rather lite-wheight in speed. Anyone tried a MySQL set-up locally on a MBP?

Me on my macbook pro. The server was installed on configured in my Linux desktop for testing. It work, but take a care that wiki connection will slow down digiKam. Using ethernet give better results.

Gilles Caulier

Pingu-Mann-Zɔro

Re: digikam 5.1.0 start-up hanging on OSX

In reply to this post by Gilles Caulier-4

Hi all,

after not being able to carry on further with this issue, I returned again today and installed DK 3.5.0.

The reading of the collections problem and bug 367853 is still seems to exist.

@Gilles Caulier,
"I also shared a new fresh PKG installer in this entry, if you is interested." I tried to download your suggested installer, Unfortunately The link is dead now.

Andrea: https://bugs.kde.org/show_bug.cgi?id=367853#c4 also reports to have tried it, without result.

Any new info on the issue?

System now:
DigiKam 5.3.0
MacOS Sierra, MacBookPro 17" 16GB RAM i7 CPU, 2011, 850GB SSD for Applications & 2TB HDD for Data in DVD Bay, both on same SATAIII bus.
Photos & iPhoto were not used, negating large db problems with them.
Attachment of Hangup screen -- It remains there for hours (tested up to 6):

Please see bug 367853

I also shared a new fresh PKG installer in this entry, if you is interested.

Gilles Caulier

2016-08-25 9:29 GMT+02:00 Gilles Caulier <[hidden email]>:

2016-08-24 18:58 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]>:

No. the HDD is in the DVD Bay, connected to the SATAIII bus. It has the same bus as the SSD. The older Intel-Macs (Jobs-Era) only have USB2, so USB2 attached Drives are a pain in the A. I now use a BlueRay-DVD over the USB2, in the rather few times I need it these days.

I keep Data separate from OS for obvious reasons, and removed the less needed DVD.

The only possible issue can perhaps be that the Data on the HDD is soft linked in the /Users/User-Name/Pictures directory to standard the "Pictures" directory of the OSX system. It has worked very well without any issues with all OSX 8-10 versions till now.

I heard that sqlite is rather lite-wheight in speed. Anyone tried a MySQL set-up locally on a MBP?

Me on my macbook pro. The server was installed on configured in my Linux desktop for testing. It work, but take a care that wiki connection will slow down digiKam. Using ethernet give better results.

Gilles Caulier

Pingu-Mann-Zɔro

Re: digikam 5.1.0 start-up hanging on OSX

In reply to this post by Gilles Caulier-4

Hi all,

after not being able to carry on further with this issue, I returned
again today and installed DK 3.5.0.

The reading of the collections problem and bug 367853 still seems to exist.
<https://bugs.kde.org/show_bug.cgi?id=367853>

@Gilles Caulier,
"I also shared a new fresh PKG installer in this entry, if you is
interested." I tried to download your suggested installer, Unfortunately
The link is dead now.

Andrea: https://bugs.kde.org/show_bug.cgi?id=367853#c4 also reports to
have tried it, without result.

Any new info on the issue?

System now:
DigiKam 5.3.0
MacOS Sierra, MacBookPro 17" 16GB RAM i7 CPU, 2011, 850GB SSD for
Applications & 2TB HDD for Data in DVD Bay, both on same SATAIII bus.
Photos & iPhoto were not used, negating large db problems with them.
Attachment of Hangup screen -- It remains there for hours (tested up to 6):

__________
Process: digikam [44928]
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier: digikam
Version: 5.3.0 (5.3.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: digikam [44928]
User ID: 501
OS Version: Mac OS X 10.12.2 (16C67)
___________

Regards,
Pingumann0

On 27/08/2016 10:42, Gilles Caulier wrote:

> Please see bug 367853 <https://bugs.kde.org/show_bug.cgi?id=367853>
>
> I also shared a new fresh PKG installer in this entry, if you is
> interested.
>
> Gilles Caulier
>
> 2016-08-25 9:29 GMT+02:00 Gilles Caulier <[hidden email]
> <mailto:[hidden email]>>:
>
>
>
> 2016-08-24 18:58 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]
> <mailto:[hidden email]>>:
>
> No. the HDD is in the DVD Bay, connected to the SATAIII bus.
> It has the same bus as the SSD. The older Intel-Macs
> (Jobs-Era) only have USB2, so USB2 attached Drives are a pain
> in the A. I now use a BlueRay-DVD over the USB2, in the rather
> few times I need it these days.
>
> I keep Data separate from OS for obvious reasons, and removed
> the less needed DVD.
>
> The only possible issue can perhaps be that the Data on the
> HDD is soft linked in the /Users/User-Name/Pictures directory
> to standard the "Pictures" directory of the OSX system. It has
> worked very well without any issues with all OSX 8-10 versions
> till now.
>
> I heard that sqlite is rather lite-wheight in speed. Anyone
> tried a MySQL set-up locally on a MBP?
>
>
> Me on my macbook pro. The server was installed on configured in my
> Linux desktop for testing. It work, but take a care that wiki
> connection will slow down digiKam. Using ethernet give better results.
>
> Gilles Caulier
>
>

Pingu-Mann-Zɔro

Re: digikam 5.1.0 start-up hanging on OSX

In reply to this post by Gilles Caulier-4

Hi all,

after not being able to carry on further with this issue since August
2016, I returned
again today and installed DK 3.5.0.

The reading of the collections problem and bug 367853 still seems to exist.
<https://bugs.kde.org/show_bug.cgi?id=367853>

Gilles, in response to your suggestion: "I also shared a new fresh PKG
installer in this entry, if you is interested.", I tried to download
your suggested installer, Unfortunately
the link is dead now. Andrea also reports to have tried it, without
result (https://bugs.kde.org/show_bug.cgi?id=367853#c4)

Any new info on the issue?

My system now:
DigiKam 5.3.0
MacOS Sierra, MacBookPro 17" 16GB RAM i7 CPU, 2011, 850GB SSD for
Applications & 2TB HDD for Data in DVD Bay, both on same SATAIII bus.
Photos & iPhoto were not used, negating large db problems with them.

Attachment of Hangup screen --
It remains there for hours (tested up to 6 hrs):
Screen Shot 2017-01-05 at 18.31.43.png
_________________________
Sometimes it crashes with this data from system protocol:
___________
Process: digikam [44928]
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier: digikam
Version: 5.3.0 (5.3.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: digikam [44928]
User ID: 501
OS Version: Mac OS X 10.12.2 (16C67)
___________

Regards,
Pingumann0

On 27/08/2016 10:42, Gilles Caulier wrote:

Screen Shot 2017-01-05 at 18.31.43.png (42K) Download Attachment

Gilles Caulier-4

Re: digikam 5.1.0 start-up hanging on OSX

The screenshot do not give any information to help you.

We need a console trace. Start digiKam from a console as explained here :

https://www.digikam.org/contrib

I responded to bugzilla about broken link to download 5.4.0 pre installer for MacOS :

https://bugs.kde.org/show_bug.cgi?id=367853#c8

Gilles Caulier

2017-01-07 15:16 GMT+01:00 Pingu-Mann-Zɔro <[hidden email]>:

Hi all,

after not being able to carry on further with this issue since August
2016, I returned
again today and installed DK 3.5.0.

The reading of the collections problem and bug 367853 still seems to exist.
<https://bugs.kde.org/show_bug.cgi?id=367853>

Gilles, in response to your suggestion: "I also shared a new fresh PKG
installer in this entry, if you is interested.", I tried to download
your suggested installer, Unfortunately
the link is dead now. Andrea also reports to have tried it, without
result (https://bugs.kde.org/show_bug.cgi?id=367853#c4)

Any new info on the issue?

My system now:
DigiKam 5.3.0
MacOS Sierra, MacBookPro 17" 16GB RAM i7 CPU, 2011, 850GB SSD for
Applications & 2TB HDD for Data in DVD Bay, both on same SATAIII bus.
Photos & iPhoto were not used, negating large db problems with them.

Attachment of Hangup screen --
It remains there for hours (tested up to 6 hrs):
Screen Shot 2017-01-05 at 18.31.43.png
_________________________
Sometimes it crashes with this data from system protocol:
___________
Process: digikam [44928]
Path: /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier: digikam
Version: 5.3.0 (5.3.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: digikam [44928]
User ID: 501
OS Version: Mac OS X 10.12.2 (16C67)
___________

Regards,
Pingumann0

On 27/08/2016 10:42, Gilles Caulier wrote:
> Please see bug 367853 <https://bugs.kde.org/show_bug.cgi?id=367853>
>
> I also shared a new fresh PKG installer in this entry, if you is
> interested.
>
> Gilles Caulier
>
> 2016-08-25 9:29 GMT+02:00 Gilles Caulier <[hidden email]
> <mailto:[hidden email]>>:
>
>
>
> 2016-08-24 18:58 GMT+02:00 Pingu-Mann-Zɔro <[hidden email]
> <mailto:[hidden email]>>:

>
> No. the HDD is in the DVD Bay, connected to the SATAIII bus.
> It has the same bus as the SSD. The older Intel-Macs
> (Jobs-Era) only have USB2, so USB2 attached Drives are a pain
> in the A. I now use a BlueRay-DVD over the USB2, in the rather
> few times I need it these days.
>
> I keep Data separate from OS for obvious reasons, and removed
> the less needed DVD.
>
> The only possible issue can perhaps be that the Data on the
> HDD is soft linked in the /Users/User-Name/Pictures directory
> to standard the "Pictures" directory of the OSX system. It has
> worked very well without any issues with all OSX 8-10 versions
> till now.
>
> I heard that sqlite is rather lite-wheight in speed. Anyone
> tried a MySQL set-up locally on a MBP?
>
>
> Me on my macbook pro. The server was installed on configured in my
> Linux desktop for testing. It work, but take a care that wiki
> connection will slow down digiKam. Using ethernet give better results.
>
> Gilles Caulier
>
>