-
Notifications
You must be signed in to change notification settings - Fork 170
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
Crashed: com.example.RealmQueue SIGABRT ABORT 0x00000001c823e7b0 #7420
Comments
This comment was marked as outdated.
This comment was marked as outdated.
➤ PM Bot commented: Jira ticket: RCORE-2001 |
This looks like an assertion, but I can't see any assertions in |
Before going into the background, we specifically disable the socket and give time for Realm tasks to complete, but crashes still occur. |
terminate_with_info() indicates that it's a REALM_ASSERT_EX() failing somewhere.
|
What can I do or provide any information to understand the problem? |
I would also like to emphasize once again that all crashes occur in the background. |
Doesn't this line indicate that this happens when the user closes the application? As far as I understand this line is not called when the application crashes, is it?
|
Ah yes, the main thread is inside a call to exit() when the crash is happening. This means that global variables are in the process of being destructed, and anything running on other threads is just sort of inherently broken. We try to avoid crashing when this happens to avoid generating noise, but this isn't a user-visible crash and is harmless other than that it generates crash reports. |
How to avoid this? Because I'm worried that real failures might get in here, confusing me and disturbing the stats |
How can I do the following?
As far as I understand Realm should do this for me, but as I see in practice it doesn't happen, it looks like a bug. |
If this is actually just a spurious crash during shutdown due to reading a destroyed global variable then #7467 will fix it. |
When is the new release planned? |
@tgoyne Why is it closed??? |
@sergeiromanchuk Because a fix was merged |
@kneth When will this be in realm-swift? |
With the next release. We don't offer timelines for publishing new versions, but historically we release new versions every 2-4 weeks. |
@tgoyne we are still experiencing significant volumes of crashes on v10.49.1 realm-swift which updated realm-core for this. @sergeiromanchuk are you seeing the same issue after updating? |
@harreed We'll have a release this week, so it's hard to say |
@kneth Please, reopen this ticket |
How frequently does the bug occur?
Sometimes
Description
Firebase title: realm::util::terminate(char const*, char const*, long, std::initializer_listrealm::util::Printable&&)
SIGABRT (ABORT)
This bug happens in production and it's a big problem for us, but we can't figure out what's wrong. The bug occurs 100% in BACKGROUND.
Stacktrace & log output
Can you reproduce the bug?
No
Reproduction Steps
No response
Version
10.47.0
What Atlas Services are you using?
Local Database only
Are you using encryption?
No
Platform OS and version(s)
iOS 12-17
Build environment
Xcode version: 14.2-15.2
Dependency manager and version: Cocoapods 1.15.2
The text was updated successfully, but these errors were encountered: