https://bugs.kde.org/show_bug.cgi?id=500697
b...@mogwai.be changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #3 from b...@mogwai.be ---
Thanks for the report.
My first coarse analysis: Kasts is actually not really frozen, it's just
re-trying failed database transactions with an increasing time between
attempts. But, if there are many failing transactions, I can see how the total
waiting time would explode, which makes it seem like it's completely
unresponsive.
This is a new feature on the master branch, but I see now that the app probably
needs to give some feedback when this happens. Also, does the UI stay
responsive, or does it also hang? Since these db transactions are running in
separate threads, I would expect the UI to stay responsive.
Anyway, it seems like the root cause is a "corruption" of your database, which
explains why this doesn't happen on other systems. I'll try and have a look at
your database later to pinpoint why that has happened (so the cause can also be
addressed, potentially).
--
You are receiving this mail because:
You are watching all bug changes.
