Seems that the debugger creates so much content, that the akonadiconsole hangs after some time. When the debugger is active, it slowly becomes unresponsive and after a while the application can only be exited by killing the process. Since the debugger remembers its stat (enabled / disabled) it is very often that i forgot to turn the debugger of before exiting and i face this issue in the next akonadiconsole session. Reproducible: Always
forgot to mention that this is actually 4.13.1, but the version was not selectable at the time of bug creation.
This is a known problem that annoys every Akonadi developer :-) The problem is in the Qt component, that simply is not able to deal with that much richtext data.
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
still valid for 5.3.1
We switched to a model in 18.08, so unless you try to resize columns, it keeps Akonadi Console responsive even with a long logging session.