Segv on start

[Nephos]

Hi,

sorry no time for more explanations, but I find out a segv. Here the valgrind trace.
I just added a folder via the gui.

(nitrogen:23447): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion 'dest_height > 0' failed
==23447== Thread 4:
==23447== Invalid read of size 8
==23447==    at 0x5EFDBA4: Gdk::Pixbuf::get_option(Glib::ustring const&) const (in /usr/lib/libgdkmm-2.4.so.1.1.0)
==23447==    by 0x41ABC0: ??? (in /usr/bin/nitrogen)
==23447==    by 0x6394A4C: ??? (in /usr/lib/libglibmm-2.4.so.1.3.0)
==23447==    by 0x4EA5344: ??? (in /usr/lib/libglib-2.0.so.0.4800.2)
==23447==    by 0x75BB453: start_thread (in /usr/lib/libpthread-2.24.so)
==23447==    by 0x78B97DE: clone (in /usr/lib/libc-2.24.so)
==23447==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==23447== 
==23447== 
==23447== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==23447==  Access not within mapped region at address 0x0
==23447==    at 0x5EFDBA4: Gdk::Pixbuf::get_option(Glib::ustring const&) const (in /usr/lib/libgdkmm-2.4.so.1.1.0)
==23447==    by 0x41ABC0: ??? (in /usr/bin/nitrogen)
==23447==    by 0x6394A4C: ??? (in /usr/lib/libglibmm-2.4.so.1.3.0)
==23447==    by 0x4EA5344: ??? (in /usr/lib/libglib-2.0.so.0.4800.2)
==23447==    by 0x75BB453: start_thread (in /usr/lib/libpthread-2.24.so)
==23447==    by 0x78B97DE: clone (in /usr/lib/libc-2.24.so)
==23447==  If you believe this happened as a result of a stack
==23447==  overflow in your program's main thread (unlikely but
==23447==  possible), you can try to increase the size of the
==23447==  main thread stack using the --main-stacksize= flag.
==23447==  The main thread stack size used in this run was 8388608.
==23447== 
==23447== HEAP SUMMARY:
==23447==     in use at exit: 4,375,526 bytes in 49,209 blocks
==23447==   total heap usage: 506,878 allocs, 457,669 frees, 294,469,947 bytes allocated
==23447== 
==23447== LEAK SUMMARY:
==23447==    definitely lost: 2,560 bytes in 4 blocks
==23447==    indirectly lost: 13,309 bytes in 545 blocks
==23447==      possibly lost: 6,948 bytes in 61 blocks
==23447==    still reachable: 4,186,925 bytes in 47,525 blocks
==23447==                       of which reachable via heuristic:
==23447==                         length64           : 27,704 bytes in 377 blocks
==23447==                         newarray           : 2,368 bytes in 68 blocks
==23447==                         multipleinheritance: 4,848 bytes in 101 blocks
==23447==         suppressed: 0 bytes in 0 blocks
==23447== Rerun with --leak-check=full to see details of leaked memory
==23447== 
==23447== For counts of detected and suppressed errors, rerun with: -v
==23447== Use --track-origins=yes to see where uninitialised values come from
==23447== ERROR SUMMARY: 472267 errors from 19 contexts (suppressed: 25841 from 20)

[daf]

Looks like Nitrogen is trying to create thumbnails of your added directory. Maybe it's picking up a file in there that the GDK pixbuf library doesn't like? Can you add a different directory without issue? Also, are you running master or last release (years ago)?

[Nephos]

I'm using the 1.5.2 version (no nitrogen --version ?)

I's happening each time I add this specific folder (too many files to handle myself), but it's okay with others.
I also know there is at least one or two corrupted files in there.