You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reproduce: build 32-bit arm version of the library and try to use.
Regression:
v1.9.0: no issues
v1.12.0: fails.
The proposed solution is to use atomic.AlignedInt64 instead of int64 in the MemoryBackend struct, or reorder len and buf, ideally -- do both, to reduce waste of space on padding.
Quoting analysis from the linked post:
I believe this is an issue in storj.io/uplink, which was upgraded from v1.9.0 to v1.12.0 for CLI 3.2.1: gilbertchen/duplicacy@7cc1b42
Please look at this thread:
https://forum.duplicacy.com/t/duplicacy-3-2-2-crashes-on-arm-32-bit/8024/7
To reproduce: build 32-bit arm version of the library and try to use.
Regression:
The proposed solution is to use
atomic.AlignedInt64
instead ofint64
in theMemoryBackend
struct, or reorderlen
andbuf
, ideally -- do both, to reduce waste of space on padding.Quoting analysis from the linked post:
The text was updated successfully, but these errors were encountered: