https://bugs.kde.org/show_bug.cgi?id=431951
griffiths_a...@icloud.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #135103|0 |1
is obsolete| |
Attachment #135120|0 |1
is obsolete| |
--- Comment #31 from griffiths_a...@icloud.com ---
Created attachment 135802
--> https://bugs.kde.org/attachment.cgi?id=135802&action=edit
Timestamped log showing UI lockup delay during possible mutex contention
More debugging info.
Build http://commits.kde.org/digikam/46fd680f2328c7ff3c55a0b538271c326c781063
Invoke digikam thru ts (timestamp input)
$ gdb digikam | ts | tee digikam_timestamped_log.txt
With this run I have attempted to timestamp the gdb output in order to
accurately work out the delay during which the UI is unresponsive (accounting
for the time in GDB examining the backtraces and threads.
In every case where I have performed this I have found that the UI is locked
while the main thread and the "DBJobsThread" are contending for a mutex (to my
eye...)
Overall there is a delay of 14 seconds, which occurs randomly, and usually at
the most inconvenient point.
My comments in the attached file are prefixed **
--
You are receiving this mail because:
You are watching all bug changes.
