Syncthing v1.4.0-rc.5 Release Notes

Release Date: 2020-02-14 // about 4 years ago
  • v1.4.0

    Important changes

    A new config option maxConcurrentIncomingRequestKiB has been added to
    limit the maximum amount of request data being concurrently processed due
    ๐Ÿ”€ to incoming requests. This limits Syncthing's peak RAM usage when there
    0๏ธโƒฃ are many connected devices all requesting file data. The default is 256
    MiB.

    ๐Ÿšš The config option maxConcurrentScans has been removed and replaced a new
    config option maxFolderConcurrency. In addition to just limiting
    ๐Ÿ”€ concurrent scans it now also limits concurrent sync operations. The
    0๏ธโƒฃ default is the number of available CPU threads ("GOMAXPROCS").

    ๐Ÿ”€ Syncthing now always runs the monitor process, which previously was
    disabled with -no-restart. This facilitates crash reporting and makes
    ๐ŸŒฒ logging behave more consistently. The observed behavior with -no-restart
    should be the same as before but the internals differ.

    The database schema has been improved and will result in a migration plus
    โฌ†๏ธ compaction at first startup after the upgrade.

    ๐Ÿ›  Bugfixes

    • ๐Ÿง #4774: Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux)
    • ๐Ÿ”€ #5952: panic: Should never get a deleted file as needed when we don't have it
    • ๐Ÿ”€ #6281: Progress emitter uses 100% CPU
    • ๐Ÿ”€ #6289: "general SOCKS server failure" since syncthing 1.3.3
    • ๐Ÿ”€ #6300: lib/ignore: panic: runtime error: index out of range [0] with length 0
    • ๐Ÿ”€ #6335: Crash or hard shutdown can case database inconsistency, out of sync

    โœจ Enhancements

    • ๐Ÿ”€ #5786: Consider always running the monitor process
    • ๐ŸŽ #5898: Database performance: reduce duplication
    • ๐ŸŽ #5914: Limit folder concurrency to improve performance
    • ๐Ÿ”€ #6302: Avoid thundering herd issue by global request limiter