[darktable-dev] Re: crash on exporting a file
/tmp/darktable_bt_D4NDQY.txt 2016-10-30 21:46 GMT+00:00 João Horta : > Darktable-git 2.1.0+2119 g50ebe5a > > > jmhorta@Ubuntu1604:~$ darktable > > (darktable:11094): Gtk-WARNING **: gtk_disable_setlocale() must be called > before gtk_init() > [New LWP 11095] > [New LWP 11096] > [New LWP 11097] > [New LWP 11098] > [New LWP 11099] > [New LWP 11100] > [New LWP 11101] > [New LWP 11102] > [New LWP 11107] > [New LWP 11108] > [New LWP 0] > [New LWP 1] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > 0x7f9ca984db5d in poll () at ../sysdeps/unix/syscall-template.S:84 > 84 ../sysdeps/unix/syscall-template.S: No such file or directory. > backtrace written to /tmp/darktable_bt_D4NDQY.txt > Falha de segmentação > jmhorta@Ubuntu1604:~$ > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org this is darktable 2.1.0+2119~g50ebe5a reporting a segfault: #0 0x7f9ca984db5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9ca948c39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9ca948c722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9ca8d24395 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x7f9ca9e98d4c in dt_gui_gtk_run (gui=) at /home/jmhorta/darktable/src/gui/gtk.c:981 #5 0x004007ca in main (argc=, argv=) at /home/jmhorta/darktable/src/main.c:25 Thread 13 (Thread 0x7f9c5d794700 (LWP 1)): #0 0x7f9ca44dfd22 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1 No symbol table info available. #1 0x7f9c6f3290dc in modify_roi_in._omp_fn.8 () at /home/jmhorta/darktable/src/iop/lens.c:894 x = y = bufptr = roi_out = 0x7f9c8af38c30 bufsize = buf = modifier = 0x7f9c84028c50 xm = inf ym = inf xM = -inf yM = -inf #2 0x7f9ca44dd43e in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1 No symbol table info available. #3 0x7f9ca9b2370a in start_thread (arg=0x7f9c5d794700) at pthread_create.c:333 __res = pd = 0x7f9c5d794700 now = unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140309559854848, 2307577186183200191, 0, 140310322891503, 8388608, 140309400916944, -2360286650354975297, -2360033135981969985}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = pagesize_m1 = sp = freesize = __PRETTY_FUNCTION__ = "start_thread" #4 0x7f9ca985982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 No locals. Thread 12 (Thread 0x7f9c5cb43700 (LWP 0)): #0 0x7f9ca44dfb4f in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1 No symbol table info available. #1 0x7f9ca44dd418 in ?? () from /usr/lib/x86_64-linux-gnu/libgomp.so.1 No symbol table info available. #2 0x7f9ca9b2370a in start_thread (arg=0x7f9c5cb43700) at pthread_create.c:333 __res = pd = 0x7f9c5cb43700 now = unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140309546940160, 2307577186183200191, 0, 140725987964671, 140309546940864, 1, -2360290473412739649, -2360033135981969985}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = pagesize_m1 = sp = freesize = __PRETTY_FUNCTION__ = "start_thread" #3 0x7f9ca985982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 No locals. Thread 11 (Thread 0x7f9c5df95700 (LWP 11108)): #0 0x7f9ca984db5d in poll () at ../sysdeps/unix/syscall-template.S:84 No locals. #1 0x7f9ca948c39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x7f9ca948c722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #3 0x7f9ca9eca934 in lua_thread_main (data=) at /home/jmhorta/darktable/src/lua/call.c:575 No locals. #4 0x7f9ca94b2bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #5 0x7f9ca9b2370a in start_thread (arg=0x7f9c5df95700) at pthread_create.c:333 __res = pd = 0x7f9c5df95700 now = unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140309568247552, 2307577186183200191, 0, 140725987952479, 140309568248256, 0, -2360287753624699457, -2360033135981969985}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = pagesize_m1 = sp = freesize = __PRETTY_FUNCTION__ = "start_thread" #6 0x7f9ca985982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 No locals. Thread 10 (T
[darktable-dev] crash on exporting a file
Darktable-git 2.1.0+2119 g50ebe5a jmhorta@Ubuntu1604:~$ darktable (darktable:11094): Gtk-WARNING **: gtk_disable_setlocale() must be called before gtk_init() [New LWP 11095] [New LWP 11096] [New LWP 11097] [New LWP 11098] [New LWP 11099] [New LWP 11100] [New LWP 11101] [New LWP 11102] [New LWP 11107] [New LWP 11108] [New LWP 0] [New LWP 1] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f9ca984db5d in poll () at ../sysdeps/unix/syscall-template.S:84 84 ../sysdeps/unix/syscall-template.S: No such file or directory. backtrace written to /tmp/darktable_bt_D4NDQY.txt Falha de segmentação jmhorta@Ubuntu1604:~$ ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Gaussian Display Error
On Sun, Oct 30, 2016 at 3:28 PM, David Vincent-Jones wrote: > Yes, this is an x-trans raw file I'm mostly asking, can anyone reproduce this with bayer raw? > and yes NaNs are in console output as > below: > > [dev_pixelpipe] module `lowpass' outputs NaNs! [preview] > [dev_pixelpipe] module `lowpass' min: (0.00; -128.00; -128.00) > max: (100.00; 128.00; 128.00) [preview] > [dev_pixelpipe] module `output color profile' outputs NaNs! [preview] > [dev_pixelpipe] module `output color profile' min: (0.00; 0.00; > 0.00) max: (1.329883; 1.130938; 1.493263) [preview] > [dev_pixelpipe] module `velvia' outputs NaNs! [preview] > [dev_pixelpipe] module `velvia' min: (0.00; 0.00; 0.00) max: > (1.00; 1.00; 1.00) [preview][dev_pixelpipe] module `lowpass' > outputs NaNs! [preview] > [dev_pixelpipe] module `lowpass' min: (0.00; -128.00; -128.00) > max: (100.00; 128.00; 128.00) [preview] > [dev_pixelpipe] module `output color profile' outputs NaNs! [preview] > [dev_pixelpipe] module `output color profile' min: (0.00; 0.00; > 0.00) max: (1.329883; 1.130938; 1.493263) [preview] > [dev_pixelpipe] module `velvia' outputs NaNs! [preview] > [dev_pixelpipe] module `velvia' min: (0.00; 0.00; 0.00) max: > (1.00; 1.00; 1.00) [preview] > > > > On 10/30/2016 01:53 AM, Roman Lebedev wrote: >> >> Does all of you expirience the problem with X-Trans sensor? >> Or with Bayer too? >> >> For x-trans: https://redmine.darktable.org/issues/11272 >> For bayer need reproducer. >> Hint: you can run darktable as `darktable -d nan` and look for >> "Module xyz outputs NaNs!" in the console output." >> >> Roman. >> >> On Sun, Oct 30, 2016 at 11:21 AM, David Vincent-Jones >> wrote: >>> >>> I opened dt (with gdb) using an image that showed the problem yesterday >>> and >>> it was still apparent at start up ... I switched several times between >>> gaussian and bilateral and the problem was clearly indicated; the 2 >>> locations blacked-out and reapeared with the change. >>> >>> Nothing unusual in the gdb listing. >>> >>> Tried to adjust memory settings (8 gb on this machine) ... no change. >>> >>> 2.1.pre+git2000.f63e5ce-1.1 Opensuse 42.1 >>> >>> >>> On 10/29/2016 10:59 AM, Patrick Shanahan wrote: * David Vincent-Jones [10-29-16 12:33]: > > I find that if gaussian curve is used either with shad/high or lowpass > the > display of the histogram is lost also the top-left overall image. > > I first noticed this with shad/high and found the situation was > corrected > when I switched to bilateral filter. seems also to happen with perspective correction on 19c3415, but not all the time, and is still active/usable to adjust exposure. it also will reappear when accessing some other modules. >>> >>> ___ >>> 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 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
Re: [darktable-dev] Gaussian Display Error
Yes, this is an x-trans raw file and yes NaNs are in console output as below: [dev_pixelpipe] module `lowpass' outputs NaNs! [preview] [dev_pixelpipe] module `lowpass' min: (0.00; -128.00; -128.00) max: (100.00; 128.00; 128.00) [preview] [dev_pixelpipe] module `output color profile' outputs NaNs! [preview] [dev_pixelpipe] module `output color profile' min: (0.00; 0.00; 0.00) max: (1.329883; 1.130938; 1.493263) [preview] [dev_pixelpipe] module `velvia' outputs NaNs! [preview] [dev_pixelpipe] module `velvia' min: (0.00; 0.00; 0.00) max: (1.00; 1.00; 1.00) [preview][dev_pixelpipe] module `lowpass' outputs NaNs! [preview] [dev_pixelpipe] module `lowpass' min: (0.00; -128.00; -128.00) max: (100.00; 128.00; 128.00) [preview] [dev_pixelpipe] module `output color profile' outputs NaNs! [preview] [dev_pixelpipe] module `output color profile' min: (0.00; 0.00; 0.00) max: (1.329883; 1.130938; 1.493263) [preview] [dev_pixelpipe] module `velvia' outputs NaNs! [preview] [dev_pixelpipe] module `velvia' min: (0.00; 0.00; 0.00) max: (1.00; 1.00; 1.00) [preview] On 10/30/2016 01:53 AM, Roman Lebedev wrote: Does all of you expirience the problem with X-Trans sensor? Or with Bayer too? For x-trans: https://redmine.darktable.org/issues/11272 For bayer need reproducer. Hint: you can run darktable as `darktable -d nan` and look for "Module xyz outputs NaNs!" in the console output." Roman. On Sun, Oct 30, 2016 at 11:21 AM, David Vincent-Jones wrote: I opened dt (with gdb) using an image that showed the problem yesterday and it was still apparent at start up ... I switched several times between gaussian and bilateral and the problem was clearly indicated; the 2 locations blacked-out and reapeared with the change. Nothing unusual in the gdb listing. Tried to adjust memory settings (8 gb on this machine) ... no change. 2.1.pre+git2000.f63e5ce-1.1 Opensuse 42.1 On 10/29/2016 10:59 AM, Patrick Shanahan wrote: * David Vincent-Jones [10-29-16 12:33]: I find that if gaussian curve is used either with shad/high or lowpass the display of the histogram is lost also the top-left overall image. I first noticed this with shad/high and found the situation was corrected when I switched to bilateral filter. seems also to happen with perspective correction on 19c3415, but not all the time, and is still active/usable to adjust exposure. it also will reappear when accessing some other modules. ___ 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 developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Gaussian Display Error
Does all of you expirience the problem with X-Trans sensor? Or with Bayer too? For x-trans: https://redmine.darktable.org/issues/11272 For bayer need reproducer. Hint: you can run darktable as `darktable -d nan` and look for "Module xyz outputs NaNs!" in the console output." Roman. On Sun, Oct 30, 2016 at 11:21 AM, David Vincent-Jones wrote: > I opened dt (with gdb) using an image that showed the problem yesterday and > it was still apparent at start up ... I switched several times between > gaussian and bilateral and the problem was clearly indicated; the 2 > locations blacked-out and reapeared with the change. > > Nothing unusual in the gdb listing. > > Tried to adjust memory settings (8 gb on this machine) ... no change. > > 2.1.pre+git2000.f63e5ce-1.1 Opensuse 42.1 > > > On 10/29/2016 10:59 AM, Patrick Shanahan wrote: >> >> * David Vincent-Jones [10-29-16 12:33]: >>> >>> I find that if gaussian curve is used either with shad/high or lowpass >>> the >>> display of the histogram is lost also the top-left overall image. >>> >>> I first noticed this with shad/high and found the situation was corrected >>> when I switched to bilateral filter. >> >> seems also to happen with perspective correction on 19c3415, but not all >> the time, and is still active/usable to adjust exposure. it also will >> reappear when accessing some other modules. >> > > ___ > 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
Re: [darktable-dev] Gaussian Display Error
I opened dt (with gdb) using an image that showed the problem yesterday and it was still apparent at start up ... I switched several times between gaussian and bilateral and the problem was clearly indicated; the 2 locations blacked-out and reapeared with the change. Nothing unusual in the gdb listing. Tried to adjust memory settings (8 gb on this machine) ... no change. 2.1.pre+git2000.f63e5ce-1.1 Opensuse 42.1 On 10/29/2016 10:59 AM, Patrick Shanahan wrote: * David Vincent-Jones [10-29-16 12:33]: I find that if gaussian curve is used either with shad/high or lowpass the display of the histogram is lost also the top-left overall image. I first noticed this with shad/high and found the situation was corrected when I switched to bilateral filter. seems also to happen with perspective correction on 19c3415, but not all the time, and is still active/usable to adjust exposure. it also will reappear when accessing some other modules. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org