sipersso

1: I don't know the size of the realm file, but this is maybe something that I could add tracking for in a future update. 2: I don't. But I...

The actual call that failed is done on the main thread and does not contain any autoreleasepools. It is not a simple proof of concept app, but an example is...

> Realms are not supported on concurrent queues, which is what `global()` is. You should create a serial queue to use a Realm on a non main thread. e.g. >...

By the way @leemaguire maybe this is something that should be made a little more clear in the documentation? I just read https://docs.mongodb.com/realm/sdk/swift/advanced-guides/threading/ and there is no mention there that...

@leemaguire FIY... I have changed all background operations to use serial queues as per your recommendation. But the issue still persists. The write operation in this case is performed on...

I think all of the issues here are caused by corrupted realms. The corruption seems to have happened for 10.22.0, but I don't see many new instances of these after...

@anlaital are you using sync? or just locally? To be fair, I think the crashes for me has been limited to t a few people on the 10.22.0 update. But...

Updating won't help correct the realms that already have corruption though. There is also no API for detecting corruption. If there is corrupt data, realm will just crash because of...

@shimastripe I don't think you won't be able to reproduce this. The transaction causing corrupted data could have happened anywhere. I am seeing fewer issues now than I did in...

Still getting crashes here. It is rare but it happens. And for those that have the issue, it happens repetitively. Here is a new stack trace ``` 3 MyApp 0x6ce598...