On Wed, Jun 03, 2026 at 07:46:57PM -0400, Perry Fraser wrote:
The only other detail is it seems very rare that this issue will
reproduce itself when only syncing with the gmail channel, which is
why the above output is both an iCloud and a gmail sync.
this suggests possible undefined behavior. try injecting
valgrind/memcheck into the call, or building with -fsanitize=address
-fsanitize=undefined (the latter should change the timing less, but it
won't catch the issue if it's in a library, say openssl).
also compare the lsof output for the mbsync processes in the different
contexts. maybe there is an inherited file descriptor that somehow gets
misused.
i can't think of much more that would explain the varying behavior that
wouldn't indicate a kernel bug or hardware (memory) error.
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
