I had a similar problem. This occurred after an attempt to transfer the file via BT. There was probably a transmission error. Helped restart the BT service. More details here
https://forum.sailfishos.org/t/systemd-journald-cpu-consumption/5140
I had a similar problem. This occurred after an attempt to transfer the file via BT. There was probably a transmission error. Helped restart the BT service. More details here
https://forum.sailfishos.org/t/systemd-journald-cpu-consumption/5140