Thank you for looking into this! Germano Massullo (2018-Apr-20, excerpt): > $ gdb --args darktable > (gdb) run > > and when the crash occurs, > > (gdb) thread apply all backtrace
Attached as requested.
Further info:
* The output on the command line varies (not surprisingly in a
concurrent setting). I've seen
$ darktable
libgomp: Thread creation failed: Resource temporarily unavailable
darktable: hb-object-private.hh:154: Type* hb_object_reference(Type*)
[with Type = hb_unicode_funcs_t]: Assertion `hb_object_is_valid (obj)' failed.
Aborted (core dumped)
Also:
$ darktable
double free or corruption (fasttop)
Aborted (core dumped)
* I never see all memory being allocated (conky). Using time(1), I
see
$ time -f 'usr=%Us ker=%Ss rss=%MkB' darktable
free(): invalid pointer
Command terminated by signal 6
usr=3.61s ker=4.81s rss=940436kB
So there should be RAM left.
--
http://stefan-klinger.de o/X
Send plain text messages only, not exceeding 32kB. /\/
\
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
gdb.txt.bz2
Description: BZip2 compressed data
