Oliver Freyermuth

Sure, no problem — to decrease chances of anything else interfering, I grabbed three in a row: * [syncthing-cpu-linux-amd64-v1.27.3-224109.pprof.gz](https://github.com/syncthing/syncthing/files/14272572/syncthing-cpu-linux-amd64-v1.27.3-224109.pprof.gz) * [syncthing-cpu-linux-amd64-v1.27.3-224248.pprof.gz](https://github.com/syncthing/syncthing/files/14272571/syncthing-cpu-linux-amd64-v1.27.3-224248.pprof.gz) * [syncthing-cpu-linux-amd64-v1.27.3-224426.pprof.gz](https://github.com/syncthing/syncthing/files/14272570/syncthing-cpu-linux-amd64-v1.27.3-224426.pprof.gz)

Interesting, sure, memory fragmentation due to many rescans (after long runtimes) seems quite likely. The reason why I stumbled upon this is actually since I am performing power consumption monitoring...

Many thanks, that's very enlightening! The built-in profiler which I missed up to now is really great. :heart: I will also take a look, but I will probably not see...

For completeness, Alex has also reported this in the forums: https://forum.syncthing.net/t/slowly-increasing-cpu-usage-over-time/21639/4?u=olifre In his case, he reports that this only started to show up for him with 1.22.3, and not with...

@colingibbs1 That's a great find! It also matches Alex' observation in the forums, i.e. that the effect is new with 1.27.3, as that "return path" without a stop of the...

> Yeah, that's [protocol.ReceiveTimeout](https://github.com/syncthing/syncthing/blob/8edd67a569594bec06c395041acb7eb18f8e3b13/lib/protocol/protocol.go#L239) in action. That makes a lot of sense, I was looking for some timeout close to 5 minutes, but apparently missed this one. Indeed, in such...

Since stale bot became active again, pinging this issue — I suffer from this problem at least once a week, and have already migrated some of my use cases to...

Since stale bot became active again, pinging this issue, it is still relevant.

Since stale bot became active again, pinging this issue, it is still relevant.

Since stale bot became active again, pinging this issue, it is still very relevant.