-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assertion failure when using Set::clear/List::clear with Mixed holding an object #4774
Comments
This might be related to #4724. |
@nirinchev this is likely fixed by #4770 |
I can test against latest v11 - I'll update this tomorrow. |
Great, thanks! I would at least expect the List to be fixed, but grant that the Set might be something totally different. Either way, it would be helpful to know if anything is fixed on the latest to make sure we're tracking down the right thing. |
With the latest Core v11, I get this for the List which appears similar to the original Set issue.
|
possibly related to realm/realm-swift#7305 |
Simpler repro without sync: var item = new IntPropertyObject { Int = 10 };
var realm = GetRealm(new RealmConfiguration(Guid.NewGuid().ToString()));
var container = realm.Write(() =>
{
return realm.Add(new SyncCollectionsObject());
});
realm.Write(() =>
{
// RealmValueList is List<Mixed> property
container.RealmValueList.Add(item);
});
realm.Write(() =>
{
container.RealmValueList.Clear();
});
realm.Write(() =>
{
realm.Remove(item);
}); Here's the crash stack:
|
Fixed by #4785 |
SDK and version
SDK : .NET
Core version: 11.0.3
Observations
Mixed{True}
andMixed{Object}
The test opens 2 realms with 2 different users and performs the following:
realm1
creates a container objectrealm2
waits for sync and looks up the container objectobj1.List.Add(True)
obj2.List.Add(new IntPropertyObject)
obj2.List.Remove(obj2.List[0])
obj1.List.Clear()
- commenting that out resolves the crashes for both List and Set.Between the steps we wait for changes from the reciprocal list and verify that
obj1.List
andobj2.List
are equivalent.Crash log / stacktrace
Crash log for the list case:
Crash log for the Set case:
The text was updated successfully, but these errors were encountered: