When I tried to sync the users directory on my C drive, my computer froze after a while and had to be restarted. I want to know if there are any configurations that can limit the use of syncthing memory. Has anyone encountered this problem before
In general, the more data you sync, the more memory will Syncthing need. There are also other factors, e.g. the number of folders/devices, etc. Syncthing itself does use a lot of resources (e.g. when scanning and hashing files), so if your system isn’t exactly stable, it could definitely lead to a freeze like that.
However, I’d say that syncing a whole user folder is usually a bad idea (unless you utilise ignore patterns heavily to exclude everything but a few selected directories).
Indeed, I synchronized approximately 450GB and 500000 files, which caused my computer to freeze
Half a million files is definitely on the larger side (see https://mon.syncthing.net/). What are the specs of the machine that’s freezing? And is it freezing and coming back after a while, or just stopping?
What Syncthing version are you using? There are some known issues in certain versions that may increase resource usage.
I am using version 1.30
It won’t be restored. I checked that the System Commit memory has reached 52.6 GB, while my memory is 32GB. I can only force a restart
Please answer the questions about the hardware specifications. For example, if this is an old machine with very little RAM, then syncing this much data simply won’t work. Also, please try using the newest version of Syncthing (which is v2.1.0 as of now), because v1.30 is outdated and no longer supported.
My system version is Windows 1.0.26200, and the win32 x64 CPU is AMD Ryzen 7 7700X 8-Core Processor. The physical memory is 32GB, and when I found that it was stuck, the System Commit had reached 52.6GB
Actually, v2.1.1 is latest. But this is a good idea, especially since it will fix Excessive resource usage from case insensitivity filesystem layer · Issue #9836 · syncthing/syncthing · GitHub, which is probably your issue.
For some reason, the website still points at v2.1.0 
.