-8.51 after update - folder sync RAM and CPU 100% (solved)

[ghisler(Author)]

No, pfo.PerformOperations returns after the files have been deleted, I have just tested it! It returns after the progress bar has reached 100%. However, it seems that Windows itself starts a background thread which remains active for a while, I don't know why.

[MarcinW]

I just checked this with Sysinternals Process Explorer under Windows 2000 and Windows XP - when deleting, TC creates a thread located inside shell32.dll (2000) or shlwapi.dll (XP) - but this thread finishes almost immediately after operation end. And deleting many files doesn't create many threads.

Did you have other results? And what OS did you test?

[ghisler(Author)]

Maybe a virus scanner slowed down the deletion of the threads?

[MarcinW]

Probably not, because the author of this bug report said that "After System restart it works well".

In addition, a virus scanner scans only some file formats (let's say: executables and documents), so the question is: does the problem occur for all kinds of files that are being deleted, or only for executables and documents?

[kargol]

Back to the old topic,

the problem ist still existing.

During the deletion process only the TOTALCMD64.EXE is working (seen with Process Explorer) with appr. 70-80% workload.
The Virusscanner is not visible (not more than 5%).

A possible solution is maybe to buy a new Laptop. The current processor (Intel Core 2 Duo P8600 2.4GHz, 3MB L2, 1066MHz FSB, TDP 25W) is now 7 years old....

The note "After System restart it works well" was not correct.

Kargol

[ghisler(Author)]

If you have a backup, I recommend that you bypass the recycle bin. It's current functions in Windows are faulty, causing this CPU overload when deleting from multiple directories.

Just hold down Shift while confirming the sync copy dialog.

[kargol]

That is the easy solution, if the dialog is asking "....will you really delete / soll wirklich gelöscht werden" press and hold the shift key before mouse-click on "OK"/"JA" and the delete-process is running much faster (and without high processor load).

Thank you TC-team!