https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #118 from Marcel <maes...@gmail.com> ---
Hi all. I'm back from holiday.
I tried the process again with the latest version of Digikam
(aa4f7ce6522c1c9559619c2dd3af5207a8a451ac).
About the huge memory demand:
Great job, this is solved.
About the memory leak:
Hard to say, I think it still leaks a bit (not as much as before). Anyway, for
the moment I have enough memory that it does not crash at least because of this
leak.
About the seg fault:
Still the same. Sometimes after a few minutes and sometimes after an hour or
more. Here is the most resent backtrace:
Thread 54 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff81ffb700 (LWP 22073)]
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007ffff6af3896 in Digikam::PreviewLoadingTask::execute
(this=0x555560845610)
at
/home/marcel/Repos/digikam/core/libs/threadimageio/preview/previewtask.cpp:362
#2 0x00007ffff6b06f6e in Digikam::LoadSaveThread::run (this=0x7fffd400bf80)
at
/home/marcel/Repos/digikam/core/libs/threadimageio/fileio/loadsavethread.cpp:134
#3 0x00007ffff6b305fa in Digikam::DynamicThread::Private::run
(this=0x555557b3b590)
at /home/marcel/Repos/digikam/core/libs/threads/dynamicthread.cpp:191
#4 0x00007ffff5301f82 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007ffff52fe9d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007ffff37f8609 in start_thread (arg=<optimized out>) at
pthread_create.c:477
#7 0x00007ffff4f72103 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb)
Is there anything else I could test that helps finding this issue?
--
You are receiving this mail because:
You are watching all bug changes.
