it’s working fine. Maybe something weird with your edit - keep in mind that‘s a development build, so module code might change between builds without caring for backward compatibility.
Thanks for the info, if is working for you should work in my system as the +236 does. I will see what can I do.
current master + a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+385~gf2ebe6b26_x86_64.dmg
latest commits: Pulse · darktable-org/darktable · GitHub
this build requires at least osx 10.15; don’t forget to backup …
Hi, try again the new build and still not working on my system.
I also download the new 4.0.1 and it is working.
Looking at both, the difference that I found is the new HL recovery that is not present in 4.0.1.
And looking the latest commits in Pulse, is it correct to assume that HL recovery (and lens fun data) is the only difference between 4.1+236 and 4.0.1? Just curiosity since I will keep using 4.1.
there’s even more stuff in current master then in 4.0.1 branch. So you need to compare the commits done in current master and those done in 4.0.1 branch. (report from 4.0.x branch: This branch is 188 commits ahead, 391 commits behind master.
Also different build environment: i’m running latest Xcode and macports libraries. The official builds seems to be built with an older Xcode ad maybe macports (so they can also support older osx versions)
So without debugging there’s no hint what’s failing
Command line dev tools is downloading, will see if I am able to do something useful with it !.
And here is what I got (which I have no idea what it means:
pascual@pascuals-imac-2 ~ % lldb /Applications/darktable_2.app/Contents/MacOS/darktable
(lldb) target create “/Applications/darktable_2.app/Contents/MacOS/darktable”
Current executable set to ‘/Applications/darktable_2.app/Contents/MacOS/darktable’ (x86_64).
(lldb) run
Process 4668 launched: ‘/Applications/darktable_2.app/Contents/MacOS/darktable’ (x86_64)
(process:4668): GLib-GObject-CRITICAL **: 18:46:19.413: g_object_set: assertion ‘G_IS_OBJECT (object)’ failed
2022-09-18 18:46:19.438532+0200 darktable[4668:1072349] SecTaskLoadEntitlements failed error=22 cs_flags=20, pid=4668
2022-09-18 18:46:19.438591+0200 darktable[4668:1072349] SecTaskCopyDebugDescription: darktable[4668]/0#-1 LF=0
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
(darktable:4668): GLib-GObject-WARNING **: 18:46:20.691: invalid cast from ‘GtkMenuBar’ to ‘GtkWindow’
(darktable:4668): Gtk-CRITICAL **: 18:46:20.691: gtk_window_add_accel_group: assertion ‘GTK_IS_WINDOW (window)’ failed
2022-09-18 18:46:27.194677+0200 darktable[4668:1072349] [plugin] AddInstanceForFactory: No factory registered for id <CFUUID 0x109476110> F8BB1C28-BAE8-11D6-9C31-00039315CD46
Process 4668 stopped
- thread #1, queue = ‘com.apple.main-thread’, stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
frame #0: 0x00007ff809d6d073 libsystem_platform.dylib`_platform_strcmp + 19
libsystem_platform.dylib`:
→ 0x7ff809d6d073 <+19>: movzbq (%rdi), %rax
0x7ff809d6d077 <+23>: movzbq (%rsi), %r8
0x7ff809d6d07b <+27>: incq %rdi
0x7ff809d6d07e <+30>: incq %rsi
Target 0: (darktable) stopped.
(lldb)
Hope this can help
after that message type “up” until you can see where in the code it fails
OK here is the result of up
pascual@pascuals-imac-2 ~ % lldb /Applications/darktable.app/Contents/MacOS/darktable
(lldb) target create “/Applications/darktable.app/Contents/MacOS/darktable”
Current executable set to ‘/Applications/darktable.app/Contents/MacOS/darktable’ (x86_64).
(lldb) run
Process 5184 launched: ‘/Applications/darktable.app/Contents/MacOS/darktable’ (x86_64)
(process:5184): GLib-GObject-CRITICAL **: 22:12:51.768: g_object_set: assertion ‘G_IS_OBJECT (object)’ failed
2022-09-18 22:12:53.759044+0200 darktable[5184:1154596] SecTaskLoadEntitlements failed error=22 cs_flags=20, pid=5184
2022-09-18 22:12:53.759131+0200 darktable[5184:1154596] SecTaskCopyDebugDescription: darktable[5184]/0#-1 LF=0
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
[dt_pthread_create] info: bumping pthread’s stacksize from 524288 to 2097152
(darktable:5184): GLib-GObject-WARNING **: 22:13:02.079: invalid cast from ‘GtkMenuBar’ to ‘GtkWindow’
(darktable:5184): Gtk-CRITICAL **: 22:13:02.079: gtk_window_add_accel_group: assertion ‘GTK_IS_WINDOW (window)’ failed
2022-09-18 22:13:07.837663+0200 darktable[5184:1154596] [plugin] AddInstanceForFactory: No factory registered for id <CFUUID 0x60000022b900> F8BB1C28-BAE8-11D6-9C31-00039315CD46
Process 5184 stopped
- thread #1, queue = ‘com.apple.main-thread’, stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
frame #0: 0x00007ff809d6d073 libsystem_platform.dylib`_platform_strcmp + 19
libsystem_platform.dylib`:
→ 0x7ff809d6d073 <+19>: movzbq (%rdi), %rax
0x7ff809d6d077 <+23>: movzbq (%rsi), %r8
0x7ff809d6d07b <+27>: incq %rdi
0x7ff809d6d07e <+30>: incq %rsi
Target 0: (darktable) stopped.
(lldb) up
warning: libtemperature.so was compiled with optimization - stepping may behave oddly; variables may not be available.
frame #1: 0x0000000122e38664 libtemperature.so`generate_preset_combo(self=0x000000010de31400) at temperature.c:684:11 [opt]
(lldb)
And more ups:
(lldb) up
warning: libtemperature.so was compiled with optimization - stepping may behave oddly; variables may not be available.
frame #1: 0x0000000122e38664 libtemperature.sogenerate_preset_combo(self=0x000000010de31400) at temperature.c:684:11 [opt] (lldb) exit Quitting LLDB will kill one or more processes. Do you really want to proceed: [Y/n] n (lldb) up frame #2: 0x0000000122e3aa45 libtemperature.so
reload_defaults(module=0x000000010de31400) at temperature.c:1507:5 [opt]
(lldb) up
warning: libdarktable.dylib was compiled with optimization - stepping may behave oddly; variables may not be available.
frame #3: 0x00000001009150a9 libdarktable.dylibdt_iop_reload_defaults(module=0x000000010de31400) at imageop.c:1163:7 [opt] (lldb) up warning: libdarkroom.so was compiled with optimization - stepping may behave oddly; variables may not be available. frame #4: 0x0000000108888fe8 libdarkroom.so
enter(self=0x0000000123e219f0) at darkroom.c:3045:7 [opt]
(lldb) up
frame #5: 0x00000001009eb979 libdarktable.dylibdt_view_manager_switch_by_view(vm=<unavailable>, nv=0x0000000123e219f0) at view.c:395:23 [opt] (lldb) up frame #6: 0x00000001009eb2ea libdarktable.dylib
dt_view_manager_switch(vm=, view_name=) at view.c:233:10 [opt] [artificial]
(lldb) up
frame #7: 0x0000000100995dde libdarktable.dylib_event_button_press(widget=<unavailable>, event=0x000000010b5a8280, user_data=0x000060000332e760) at thumbtable.c:1092:5 [opt] (lldb) up frame #8: 0x0000000101882e46 libgtk-3.0.dylib
_gtk_marshal_BOOLEAN__BOXED + 97
libgtk-3.0.dylib: -> 0x101882e46 <+97>: movq %r14, %rdi 0x101882e49 <+100>: movl %eax, %esi 0x101882e4b <+102>: addq $0x8, %rsp 0x101882e4f <+106>: popq %rbx (lldb) up frame #9: 0x0000000100e4063f libgobject-2.0.0.dylib
g_closure_invoke + 199
libgobject-2.0.0.dylibg_closure_invoke: -> 0x100e4063f <+199>: movl (%rbx), %eax 0x100e40641 <+201>: shrl $0x10, %eax 0x100e40644 <+204>: andl $0x1, %eax 0x100e40647 <+207>: je 0x100e4067d ; <+261> (lldb) up frame #10: 0x0000000100e54e94 libgobject-2.0.0.dylib
signal_emit_unlocked_R + 1457
libgobject-2.0.0.dylibsignal_emit_unlocked_R: -> 0x100e54e94 <+1457>: cmpq $0x0, -0x40(%rbp) 0x100e54e99 <+1462>: je 0x100e54edd ; <+1530> 0x100e54e9b <+1464>: movq -0x40(%rbp), %rax 0x100e54e9f <+1468>: movq 0x8(%rax), %rcx (lldb) up frame #11: 0x0000000100e55bab libgobject-2.0.0.dylib
g_signal_emit_valist + 1926
libgobject-2.0.0.dylib`g_signal_emit_valist:
→ 0x100e55bab <+1926>: movq (%r15), %rdi
0x100e55bae <+1929>: callq 0x100e5bdca ; g_type_value_table_peek
0x100e55bb3 <+1934>: movq %rax, %r8
0x100e55bb6 <+1937>: movq 0x30(%rax), %rax
(lldb)
ok, there seems to be something with white balance (temperature.c)
So you might check if that’s caused just by one image or a general issue. To do this you can run darktable -d Image -d params to check which image raises the crash.
Then run the latest working darktable, clear the history stack of that image (after exporting and backup of the xmp) and see if dt crashes again.
Ince you know if it’s caused by a specific history stack or in general you can raise an issue at github so a developer can have a look what’s exactly happening (please provide the image and the xmp that failed - so a dev can try to reproduce)
But since you‘ve installed commandline tools now, you also can build darktable yourself following darktable/BUILD.txt at master · darktable-org/darktable · GitHub.
I did your suggestions and it seems to be a general problem, thus I will raise at issue at github.
Building myself is a challenge but will try.
Thank you for your help
For information,I raised an issue at GitHub:
# darktable current master (Mac OSX build) crashes when opening an image in darkroom. White balance issue ? #12527
and as a side observation the issue number is a prime one
I don’t want to pollute this thread, just a quick question: I followed the instructions to build and when using cmake I have an error which suggests that I am missing OpenMP_C. However there is no mentioning of openMp in the instructions. Any suggestions?
Thank you
openmp is provided by libomp
you can try port installed libomp
to see if it’s proper installed.
or ls -la /opt/local/include/libomp
or ls -la /opt/local/lib/libomp
Great, thank you
based on zurdos issue report bugfixed (#12530) current master + a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+401~gf37405bc3_x86_64.dmg
latest commits: Pulse · darktable-org/darktable · GitHub
this build requires at least osx 10.15; don’t forget to backup …
Excellent it is working as expected (will keep testing). I will keep the building as a learning process; openmp solved as you suggested, now dealing with LLVM missing
Thank you again for the help and build.
llvm missing doesn’t matter …
current master + a couple of RF lensfun data from: Kameratrollet
darktable-4.1.0+416~g7dcf8a8c1_x86_64.dmg
latest commits: Pulse · darktable-org/darktable · GitHub
this build requires at least osx 10.15; don’t forget to backup …