Project

General

Profile

Bug #2050

Inconsistent AtSync behavior with bound arrays

Added by Eric Mikida 16 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/01/2019
Due date:
% Done:

0%


Description

Reported by Jozsef from Quinoa:
He is using AtSync migration to balance multiple bound arrays. He only calls AtSync from one of the arrays. He saw behavior differences when using ResumeFromSync vs not.

When not waiting on ResumeFromSync(), if all bound array elements set usesAtSync=true, then everything worked fine (even though only one array called AtSync). If only the main array set usesAtSync=true, then there would be hangs/segfaults.

When waiting on ResumeFromSync(), he saw the opposite. Everything worked correctly if only the main array set usesAtSync=true, but hung/segfaulted if they all set it.

To my understanding, if only one of the bound arrays is calling AtSync, it should be the only one that sets usesAtSync=true, regardless of whether ResumeFromSync() is used.

He has a small test case and he is going to see if it also exhibits this problem for us.

Also available in: Atom PDF