this is a feature in k3b and does not cause an excess cpu load so is unlikely to be related to bug 51939
this is a feature in k3b and does not cause an excess cpu load so is unlikely to be related to bug 51939