Re: [darktable-dev] Random crashing - error messages GLIB, json & serialize
Hi, Please see attached backtrace file... Hope it helps. Cheers. On 2018-05-28 08:59, Tobias Ellinghaus wrote: Am Sonntag, 27. Mai 2018, 20:07:23 CEST schrieb Mark Heieis: Hi, Just loaded a days worth of shooting and doing my preliminary triage. The problem is that I'm getting the following errors but can't isolate as to when or what's making it happen. GLib:ERROR:ghash.c:373:g_hash_table_lookup_node: assertion failed: (hash_table->ref_count > 0) Aborted (core dumped) in addition, not knowing if its related, I'm also getting the following within the same session but doesn't make dt crash: (darktable:18557): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:18557): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed The json errors occur many times then finally the glib core dump. and [xmp_write] /home/.../IMG_6950.CR2.xmp: caught exiv2 exception '[xmp_write] failed to serialize xmp data' [xmp_write] /home/.../IMG_6948.CR2.xmp: caught exiv2 exception '[xmp_write] failed to serialize xmp data' Tell me what you need and I'll try and get it. Please check if darktable managed to write a backtrace to /tmp/ Using 2.4.3 on Fedora 4.16.7-100.fc26.x86_64 and KDE5 Regards Tobias ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org this is darktable 2.4.3 reporting a segfault: warning: Currently logging to /tmp/darktable_bt_PGO8JZ.txt. Turn the logging off and on to make the new setting effective. #0 0x7fb255611ce7 in waitpid () at /lib64/libpthread.so.0 #1 0x7fb255901780 in _dt_sigsegv_handler () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7fb255261a80 in () at /lib64/libc.so.6 #3 0x7fb2530983ce in g_type_check_instance_is_a () at /lib64/libgobject-2.0.so.0 #4 0x7fb25467627e in gtk_widget_get_allocation () at /lib64/libgtk-3.so.0 #5 0x7fb2559a915b in _ui_panel_size_changed () at /usr/bin/../lib64/darktable/libdarktable.so #6 0x7fb25307330d in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #7 0x7fb25308596e in signal_emit_unlocked_R () at /lib64/libgobject-2.0.so.0 #8 0x7fb25308e195 in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #9 0x7fb25308eaff in g_signal_emit () at /lib64/libgobject-2.0.so.0 #10 0x7fb253077594 in g_object_dispatch_properties_changed () at /lib64/libgobject-2.0.so.0 #11 0x7fb2543f5706 in gtk_adjustment_dispatch_properties_changed () at /lib64/libgtk-3.so.0 #12 0x7fb253076f3e in g_object_notify_queue_thaw () at /lib64/libgobject-2.0.so.0 #13 0x7fb253079c4b in g_object_thaw_notify () at /lib64/libgobject-2.0.so.0 #14 0x7fb25466781f in gtk_viewport_allocate () at /lib64/libgtk-3.so.0 #15 0x7fb254462346 in gtk_css_gadget_allocate () at /lib64/libgtk-3.so.0 #16 0x7fb254668084 in gtk_viewport_size_allocate () at /lib64/libgtk-3.so.0 #17 0x7fb254675df3 in gtk_widget_size_allocate_with_baseline () at /lib64/libgtk-3.so.0 #18 0x7fb2545aa846 in gtk_scrolled_window_allocate_child () at /lib64/libgtk-3.so.0 #19 0x7fb2545ab9d3 in gtk_scrolled_window_allocate () at /lib64/libgtk-3.so.0 #20 0x7fb254462346 in gtk_css_gadget_allocate () at /lib64/libgtk-3.so.0 #21 0x7fb2545a830a in gtk_scrolled_window_size_allocate () at /lib64/libgtk-3.so.0 #22 0x7fb254675df3 in gtk_widget_size_allocate_with_baseline () at /lib64/libgtk-3.so.0 #23 0x7fb25440c0ca in gtk_box_size_allocate_no_center () at /lib64/libgtk-3.so.0 #24 0x7fb25440c407 in gtk_box_allocate_contents () at /lib64/libgtk-3.so.0 #25 0x7fb254462346 in gtk_css_gadget_allocate () at /lib64/libgtk-3.so.0 #26 0x7fb25440d845 in gtk_box_size_allocate () at /lib64/libgtk-3.so.0 #27 0x7fb254675df3 in gtk_widget_size_allocate_with_baseline () at /lib64/libgtk-3.so.0 #28 0x7fb2544df4f5 in gtk_grid_allocate () at /lib64/libgtk-3.so.0 #29 0x7fb254462346 in gtk_css_gadget_allocate () at /lib64/libgtk-3.so.0 #30 0x7fb2544dd243 in gtk_grid_size_allocate () at /lib64/libgtk-3.so.0 #31 0x7fb254675df3 in gtk_widget_size_allocate_with_baseline () at /lib64/libgtk-3.so.0 #32 0x7fb25440c0ca in gtk_box_size_allocate_no_center () at /lib64/libgtk-3.so.0 #33 0x7fb25440c407 in gtk_box_allocate_contents () at /lib64/libgtk-3.so.0 #34 0x7fb254462346 in gtk_css_gadget_allocate () at /lib64/libgtk-3.so.0 #35 0x7fb25440d845 in gtk_box_size_allocate () at /lib64/libgtk-3.so.0 #36 0x7fb254675df3 in gtk_widget_size_allocate_with_baseline () at /lib64/libgtk-3.so.0 #37 0x7fb25468c333 in gtk_window_size_allocate () at /lib64/libgtk-3.so.0 #38 0x7fb25307330d in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #39 0x
Re: [darktable-dev] Random crashing - error messages GLIB, json & serialize
Unfortunately, no back trace files. I'll keep trying. m. On 2018-05-28 08:59, Tobias Ellinghaus wrote: > Am Sonntag, 27. Mai 2018, 20:07:23 CEST schrieb Mark Heieis: >> Hi, >> >> Just loaded a days worth of shooting and doing my preliminary triage. >> The problem is that I'm getting the following errors but can't isolate >> as to when or what's making it happen. >> >> GLib:ERROR:ghash.c:373:g_hash_table_lookup_node: assertion failed: >> (hash_table->ref_count > 0) >> Aborted (core dumped) >> >> in addition, not knowing if its related, I'm also getting the following >> within the same session but doesn't make dt crash: >> >> (darktable:18557): Json-CRITICAL **: json_object_ref: assertion >> 'object->ref_count > 0' failed >> (darktable:18557): Json-CRITICAL **: json_object_has_member: assertion >> 'object != NULL' failed >> >> The json errors occur many times then finally the glib core dump. >> >> and >> >> [xmp_write] /home/.../IMG_6950.CR2.xmp: caught exiv2 exception >> '[xmp_write] failed to serialize xmp data' >> [xmp_write] /home/.../IMG_6948.CR2.xmp: caught exiv2 exception >> '[xmp_write] failed to serialize xmp data' >> >> Tell me what you need and I'll try and get it. > Please check if darktable managed to write a backtrace to /tmp/ > >> Using 2.4.3 on Fedora 4.16.7-100.fc26.x86_64 and KDE5 >> >> Regards > Tobias ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Random crashing - error messages GLIB, json & serialize
Hi, Just loaded a days worth of shooting and doing my preliminary triage. The problem is that I'm getting the following errors but can't isolate as to when or what's making it happen. GLib:ERROR:ghash.c:373:g_hash_table_lookup_node: assertion failed: (hash_table->ref_count > 0) Aborted (core dumped) in addition, not knowing if its related, I'm also getting the following within the same session but doesn't make dt crash: (darktable:18557): Json-CRITICAL **: json_object_ref: assertion 'object->ref_count > 0' failed (darktable:18557): Json-CRITICAL **: json_object_has_member: assertion 'object != NULL' failed The json errors occur many times then finally the glib core dump. and [xmp_write] /home/.../IMG_6950.CR2.xmp: caught exiv2 exception '[xmp_write] failed to serialize xmp data' [xmp_write] /home/.../IMG_6948.CR2.xmp: caught exiv2 exception '[xmp_write] failed to serialize xmp data' Tell me what you need and I'll try and get it. Using 2.4.3 on Fedora 4.16.7-100.fc26.x86_64 and KDE5 Regards ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] RawSpeed:Unable to find camera in database: 'Canon' 'Canon EOS 5D Mark II' 'dng'
2.2.5-2 (Fedora) On 2018-01-22 08:54, Roman Lebedev wrote: On Mon, Jan 22, 2018 at 7:49 PM, Mark Heieis <mhei...@alois.ca> wrote: Hi, I'm getting this message: "RawSpeed:Unable to find camera in database: 'Canon' 'Canon EOS 5D Mark II' 'dng'" Just ignore that message. Which dt version is that? The dng file is a resultant output of using magic latern's dual iso and processing with cr2hdr. Here's a link to a dng file https://www.dropbox.com/s/i3vb3ars0nfpxso/IMG_1636.DNG?dl=0 I'll delete the link in a few weeks. Regards. Roman. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] RawSpeed:Unable to find camera in database: 'Canon' 'Canon EOS 5D Mark II' 'dng'
Hi, I'm getting this message: "RawSpeed:Unable to find camera in database: 'Canon' 'Canon EOS 5D Mark II' 'dng'" The dng file is a resultant output of using magic latern's dual iso and processing with cr2hdr. Here's a link to a dng file https://www.dropbox.com/s/i3vb3ars0nfpxso/IMG_1636.DNG?dl=0 I'll delete the link in a few weeks. Regards. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Flash data in "image information" panel?
Hi, Is there a reason (beyond UI space) that flash information is not displayed? Or is it somewhere else that I'm missing? Either way, it would be rather nice if flash data was included in the image information panel. Thanks. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] All of a sudden, darktable Thread Seg faults
I found that clinfo
also segfaulted. Further investigation showed that the amdgpu
libs had been changed. Reinstalling the few required libs
solved my issue. So I suspect that an OS upgrade clobbered
them. I placed them in /lib64 rather than in /opt/lib64 as I
have a few other programs that use opencl that didn't appear
to use the export var.
On 2017-04-08 08:23, Ulrich Pegelow
wrote:
Strange things also happen here. All of a sudden
darktable would hang during startup in the OpenCL init phase of my
AMD card (catalyst driver).
I bisected the issue and found this:
97085123a6c29bed86fc7795d527c95bd50a is the first bad commit
commit 97085123a6c29bed86fc7795d527c95bd50a
Author: Roman Lebedev <lebedev...@gmail.com>
Date: Tue Apr 4 20:51:11 2017 +0300
Rawspeed submodule update: some static analysis fixes.
:04 04 c3da68a8bc9ec1664348e969bae26540f76234c0
6a112acf0d814aa0eb4bd68f17d14f012ef94e4c M src
Quite surprising. Doesn't look like the commit is related to
OpenCL but I can reproduce that before this commit all is good and
after that darktable with AMD OpenCL doesn't start. Reverting that
commit in master makes darktable start again.
Ulrich
Am 05.04.2017 um 21:42 schrieb Roman Lebedev:
On Wed, Apr 5, 2017 at 10:29 PM, Mark
Heieis <mhei...@alois.ca> wrote:
Hi There,
Today, for some reason, darktable seg faults with the
following. I used it
yesterday and it worked fine. I may have updated the OS after
my last use
and could roll-back the update to check. Any thoughts?
Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31
13:20:22 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ darktable
[New LWP 2506]
[New LWP 2507]
[New LWP 2508]
[New LWP 2509]
[New LWP 2510]
[New LWP 2511]
[New LWP 2512]
[New LWP 2513]
[New LWP 2514]
[New LWP 2515]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0
backtrace written to /tmp/darktable_bt_XVOKYY.txt
Segmentation fault (core dumped)
~
Core dump:
this is darktable darktable-2.2.3-1.fc25 reporting a segfault:
#0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0
#1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at
/usr/bin/../lib64/darktable/libdarktable.so
#2 0x7f1b3790b990 in () at
/lib64/libc.so.6
#3 0x in ()
#4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so
So the issue *appears* to be in amd opencl blob.
You can disable opencl, that would get rid of the crash.
#5 0x7f1ae45e1afe in () at
/lib64/libamdocl64.so
#6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so
#7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so
#8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so
#9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so
#10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so
#11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so
#12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so
#13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so
#14 0x7f1ae424140e in () at /lib64/libamdocl64.so
#15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so
#16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at
/lib64/libamdocl64.so
#17 0x7f1b1c65676e in () at /lib64/libOpenCL.so
#18 0x7f1b1c658647 in () at /lib64/libOpenCL.so
#19 0x7f1b3b093ba9 in __pthread_once_slow () at
/lib64/libpthread.so.0
#20 0x7f1b1c656d31 in clGetPlatformIDs () at
Re: [darktable-dev] All of a sudden, darktable Thread Seg faults
Yep, darktable opens fine with opencl disabled, so clearly an (amd driver/lib?) opencl issue. On 2017-04-05 13:01, Mark Heieis wrote: Yes, I found that clinfo seg faults as well. So not sure if it's with the AMD libs, the open source driver piece or a kernel update that's making this happen. On 2017-04-05 12:42, Roman Lebedev wrote: On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis <mhei...@alois.ca> wrote: Hi There, Today, for some reason, darktable seg faults with the following. I used it yesterday and it worked fine. I may have updated the OS after my last use and could roll-back the update to check. Any thoughts? Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ darktable [New LWP 2506] [New LWP 2507] [New LWP 2508] [New LWP 2509] [New LWP 2510] [New LWP 2511] [New LWP 2512] [New LWP 2513] [New LWP 2514] [New LWP 2515] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0 backtrace written to /tmp/darktable_bt_XVOKYY.txt Segmentation fault (core dumped) ~ Core dump: this is darktable darktable-2.2.3-1.fc25 reporting a segfault: #0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0 #1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3790b990 in () at /lib64/libc.so.6 #3 0x in () #4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so So the issue *appears* to be in amd opencl blob. You can disable opencl, that would get rid of the crash. #5 0x7f1ae45e1afe in () at /lib64/libamdocl64.so #6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so #7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so #8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so #9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so #10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so #11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so #12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so #13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so #14 0x7f1ae424140e in () at /lib64/libamdocl64.so #15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so #17 0x7f1b1c65676e in () at /lib64/libOpenCL.so #18 0x7f1b1c658647 in () at /lib64/libOpenCL.so #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0 #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so #21 0x7f1b3f9da58b in dt_opencl_init () at /usr/bin/../lib64/darktable/libdarktable.so #22 0x7f1b3f9802be in dt_init () at /usr/bin/../lib64/darktable/libdarktable.so #23 0x560f0cb71b86 in main () Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1b1d85c700 (LWP 2514)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1b1e05d700 (LWP 2513)): #0 0x7f1b379a281d in nanosleep () at /lib64/libc.so.6 #1 0x7f1b379a276a in sleep () at /lib64/libc.so.6 #2 0x7f1b3f9e228a in dt_control_worker_kicker () at /usr/bin/../lib64/darktable/libdarktable.so #3 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1b1e85e700 (LWP 2512)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1b1f05f700 (LWP 2511)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1b1705f700 (LWP 2510)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/li
Re: [darktable-dev] All of a sudden, darktable Thread Seg faults
Yes, I found that clinfo seg faults as well. So not sure if it's with the AMD libs, the open source driver piece or a kernel update that's making this happen. On 2017-04-05 12:42, Roman Lebedev wrote: On Wed, Apr 5, 2017 at 10:29 PM, Mark Heieis <mhei...@alois.ca> wrote: Hi There, Today, for some reason, darktable seg faults with the following. I used it yesterday and it worked fine. I may have updated the OS after my last use and could roll-back the update to check. Any thoughts? Linux copernicus 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ darktable [New LWP 2506] [New LWP 2507] [New LWP 2508] [New LWP 2509] [New LWP 2510] [New LWP 2511] [New LWP 2512] [New LWP 2513] [New LWP 2514] [New LWP 2515] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f1b3b095fdb in waitpid () from /lib64/libpthread.so.0 backtrace written to /tmp/darktable_bt_XVOKYY.txt Segmentation fault (core dumped) ~ Core dump: this is darktable darktable-2.2.3-1.fc25 reporting a segfault: #0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0 #1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3790b990 in () at /lib64/libc.so.6 #3 0x in () #4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so So the issue *appears* to be in amd opencl blob. You can disable opencl, that would get rid of the crash. #5 0x7f1ae45e1afe in () at /lib64/libamdocl64.so #6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so #7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so #8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so #9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so #10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so #11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so #12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so #13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so #14 0x7f1ae424140e in () at /lib64/libamdocl64.so #15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so #17 0x7f1b1c65676e in () at /lib64/libOpenCL.so #18 0x7f1b1c658647 in () at /lib64/libOpenCL.so #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0 #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so #21 0x7f1b3f9da58b in dt_opencl_init () at /usr/bin/../lib64/darktable/libdarktable.so #22 0x7f1b3f9802be in dt_init () at /usr/bin/../lib64/darktable/libdarktable.so #23 0x560f0cb71b86 in main () Thread 11 (Thread 0x7f1b1d05b700 (LWP 2515)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1b1d85c700 (LWP 2514)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e265f in dt_control_work_res () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1b1e05d700 (LWP 2513)): #0 0x7f1b379a281d in nanosleep () at /lib64/libc.so.6 #1 0x7f1b379a276a in sleep () at /lib64/libc.so.6 #2 0x7f1b3f9e228a in dt_control_worker_kicker () at /usr/bin/../lib64/darktable/libdarktable.so #3 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1b1e85e700 (LWP 2512)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1b1f05f700 (LWP 2511)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f1b1705f700 (LWP 2510)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1b1f860700 (LWP 2509)): #0 0x7f1b3b092460 in pthread_cond_w
[darktable-dev] All of a sudden, darktable Thread Seg faults
n/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1b1f860700 (LWP 2509)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f1b20061700 (LWP 2508)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f1b20862700 (LWP 2507)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f1b21063700 (LWP 2506)): #0 0x7f1b3b092460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1b3f9e38be in dt_control_work () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3b08c6ca in start_thread () at /lib64/libpthread.so.0 #3 0x7f1b379ddf7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f1b3ff07680 (LWP 2505)): #0 0x7f1b3b095fdb in waitpid () at /lib64/libpthread.so.0 #1 0x7f1b3f9ccc40 in _dt_sigsegv_handler () at /usr/bin/../lib64/darktable/libdarktable.so #2 0x7f1b3790b990 in () at /lib64/libc.so.6 #3 0x in () #4 0x7f1ae45dfb89 in () at /lib64/libamdocl64.so #5 0x7f1ae45e1afe in () at /lib64/libamdocl64.so #6 0x7f1ae45d1b98 in () at /lib64/libamdocl64.so #7 0x7f1ae42edf69 in () at /lib64/libamdocl64.so #8 0x7f1ae42bc4d9 in () at /lib64/libamdocl64.so #9 0x7f1ae42bc54f in () at /lib64/libamdocl64.so #10 0x7f1ae42bd2c9 in () at /lib64/libamdocl64.so #11 0x7f1ae42843d8 in () at /lib64/libamdocl64.so #12 0x7f1ae42858c7 in () at /lib64/libamdocl64.so #13 0x7f1ae4285a56 in () at /lib64/libamdocl64.so #14 0x7f1ae424140e in () at /lib64/libamdocl64.so #15 0x7f1ae425cc27 in () at /lib64/libamdocl64.so #16 0x7f1ae422adbe in clIcdGetPlatformIDsKHR () at /lib64/libamdocl64.so #17 0x7f1b1c65676e in () at /lib64/libOpenCL.so #18 0x7f1b1c658647 in () at /lib64/libOpenCL.so #19 0x7f1b3b093ba9 in __pthread_once_slow () at /lib64/libpthread.so.0 #20 0x7f1b1c656d31 in clGetPlatformIDs () at /lib64/libOpenCL.so #21 0x7f1b3f9da58b in dt_opencl_init () at /usr/bin/../lib64/darktable/libdarktable.so #22 0x7f1b3f9802be in dt_init () at /usr/bin/../lib64/darktable/libdarktable.so #23 0x560f0cb71b86 in main () -- ____ Mark Heieis, MSc, MBA +1.604.250.4107 ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
