-
Notifications
You must be signed in to change notification settings - Fork 172
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
Crash on Persisted.subscript.getter #6126
Comments
Hi @NZQN23, thanks for reporting this. Are you able to share the Realm with us at [email protected]? |
Hi @ironage, unfortunately I don't have any of those Realm files myself, I just see about 3-5 crashes like this in Xcode. I had severe problems in the last months with the issue of corrupted Realm files that you have fixed lately. Is it possible that this issue now is still derived from corrupted Realm files of users still using the app? |
Hello, do you have any update on this issue? |
@NZQN23 yes, this issue could be rooted in a previously corrupted Realm. If it is due to corruption there is not a lot we can do, but if not we will need some other information to be able to track this one down, so if you keep seeing this, please continue to provide additional stack traces or any other information that could help. |
Thanks @ironage . Yes, I still see a lot of these crashes. Do you want me to post the stack traces here or send it to you via email? |
@NZQN23 please post them on this public issue so that other members of my team can help (unless the information is sensitive). |
@ironage Unfortunately, I don‘t have this information. I also don‘t have access to any corrupted Realm files. I only see 1K+ monthly crashes on iOS -.- |
@NZQN23 ok that is unfortunate, but understandable. It will likely be difficult to track down without some more information, but post what you do have and maybe a pattern will emerge. |
@NZQN23 Are you still seeing these issues occurring? |
Yes, I still get these crashes on a daily basis. But I still could not reproduce it myself. |
@bmunkholm I am using 12.13.0 - do you want me to post the other stack traces here or via email? If latter, to which address? |
@leemaguire @tgoyne I am not sure in which context the |
@NZQN23 Here is great. Feel free to add it as "Collapsible content" DetailsStacktrace.... |
The first thing we do in |
The stack trace is mostly very unremarkable; it's just the normal path for a property getter (in this case a non-optional String). The one curious bit is that the call to terminate is happening at +760, but Obj::_getrealm::StringData(realm::ColKey::Idx) is only 736 bytes in a arm64 -O3 build of 12.3.0, and quite a bit smaller in debug or O2 builds. This points to something weird going on, but I don't know what. |
Sorry, I had very bad connectivity the last two weeks. Here are some more stack traces I could find for this issue. To me they look same but they definitely are from individual crash logs.
|
I keep getting these crashes even with a newer Realm version:
|
@NZQN23 Is this issue still relevant? All these stacktraces does not provide more information, and based on what we have here there is not much to work on. |
No, I have not experienced any more of those crashes. |
Ok, thanks. I will close this issue. |
Expected results
Get attribute data from Object
Actual Results
Crash
Core version
Core version: 12.13.0
The text was updated successfully, but these errors were encountered: