Unusually high CPU

[jonsnow231]

Description
The CPU is unusually high, turning on my laptop fans. It does this seemingly randomly, and the only way to fix it is to close out of the program and open it back up again.

Steps to reproduce
I don't do anything except let it sync automatically.

Logs
20240326_2051_kDrive - Copy.log

[ClementKunz]

I do not see anything wrong in your log, just about 250 update of the same file that has been correctly synchronized. Every time a file is modified, a new synchronisation start.
Please, if you notice any reproducible issue, let us now about it.

[ChristopheLarchier]

Your Zim editor makes autosaves frequently (by default each time a character is modified in the file or the cursor is moved, see https://zim-wiki.org/) which causes the file synchronization.
You may be able to disable this autosave or otherwise work outside of the sync folder.

[supertoni3c]

I experienced the same problem. Regardless if the app is syncing or not the RAM usage is at least 15 GB and the CPU usage is also very high. However, closing the app doesn't solve it. It happens on Fedora 40 beta with Gnome.

PS After further investigation, I noticed that it happened twice during initial synchronisation. Interestingly, it happened simultaneously with many errors about read/write permissions. Now, everything appears to be okay.

[herve-er]

Hello @supertoni3c, thank you for your feedback and patience regarding this matter. It appears that your issue might be connected to an existing problem reported in #204.

Files are first downloaded into the temporary (tmp) folder, which is in certain Linux distributions, including Fedora in the system's RAM. The read/write errors you're experiencing are due to the tmp folder reaching its maximum capacity (default set to half of your total RAM size). This issue, is causing the application to fail in completing the synchronization process, leading to it looping and consuming excessive CPU resources.
Our team is looking into this issue and working towards providing a solution in future updates.

As the high CPU usage issue seems to be unrelated, we will close this issue. However, feel free to follow the progress on the related issue #204 for updates.