realm::_impl::ExternalCommitHelper::listen() (external_commit_helper.cpp:217) #6144
Comments
|
@ganesh-ananthan This is impossible to debug without further information. Can you please provide the full stacktrace? |
|
Hi Bmunkholm, Please verify this stack trace and give us the idea of why it's reaching assert. |
|
@tgoyne Have you seen this before? @ganesh-ananthan In the meantime, can you give us more information: |
|
No this is occurring only on production, while testing we were not able to reproduce it. Frequency seems 50% of hockeycrash is this. |
|
No, this isn't something we've ever seen before. The code merely asserts that no error occurred in It's also possible that it has been failing for people, but since |
|
Does hockey give you stats on if the crashes were in the foreground or background? If they're all in the background then there's more possible explanations for what's going wrong. |
|
@tgoyne hello! I was monitoring this ticket hoping for a fix. |
|
Do you have Data Protection enabled for the app? |
|
If this is the default, then yes |
|
3.16.2 (which is currently going through the release process) may fix this if it turns out the problem was just the lack of EINTR handling. It also might do nothing. |
|
We were tried all the best possibilities of realm executions , like serialising the write transaction on single queue (suggested by Ian ward). Still we are getting the crash on production. |
|
@tgoyne Any updates regarding this Crash ? Or the upcoming version (3.16.2) will resolve it ? |
|
3.16.2 is out and might fix it. If it didn’t then I’ll need to try more things. |
|
Closing this issue with no recent activity. I assume this issue has been resolved -- please let us know if that is not the case. |
|
Hello, same line reported by Crashlytics this morning in production with RealmSwift 3.17.0: |
|
Hello, same crash reproduced for me. |
|
@stennie , please, reopen this ticket. |
|
@remihillairet @Vinamor Where do you see it has crashed in Realm? And which kind of crash? |
|
#16. Realm notification listener |
|
@bmunkholm , the information I provided is enough for you to analyze the issue? |
|
There is unfortunately not much to go from without a way to repro the issue. If you have any clues to that, that would be wonderful! |
|
For now we only have one user affected among thousands. |
|
FWIW This crash is happening on our app as well, 20 users over the past 7 days. |
|
I've encountered this error with version It occurs on Realm initialization, and produces a |
|
Same issue with our production app (199 users affected)
Any guidance on how to mitigate this or if it's a fix on the way? Thanks! |
|
We have this issue as well.
I tested on the latest realm version (5.0.1). It still crashes. It reproduces 100% of the time on one of my test devices (iPod Touch 5G). Any workaround for this? |
|
@eastsss If you can reproduce this consistently we would be very interested if you can share the project with us privately and confidentially. Or if you could possible reduce it down to something minimal shareable? |
|
@bmunkholm Unfortunately this is a commercial project, I don't own it so I can't share the code. But may be there are other possible ways to debug this issue? Like logs or something? |
|
For example, what if we add some logs to Realm code and I reproduce this crash? Can this help somehow? |
|
Hmm - yeah it will likely be a painful slow process. But yeah if can can do that it would be great! |
|
Ok, then may be we should use some communication channels other than github? to solve this thing faster? |
|
There is no internal logging that would help with this. It would require that you debug it by building Realm yourself and add appropriate logs/print statements from where it crashes. So it's a little involved... |
|
ok, any hints on what should I log? or may be you can take a source code of Realm and add logs(or comments to the appropriate lines) which can help to determine the problem and then send me somehow? Then I will change them to Crashlytics logs and reproduce the crash... |
|
Pinging @ericjordanmossman or @tgoyne - perhaps one of them will be able to help with that. |
|
anybody here? :) any hints on what to log? |
With a reproduction I would download the realm-cocoa source, then If you can induce the error I would set a breakpoint here or here, depending on where it crashes. Then take note of the value of This is where I'd try to begin, but I have a limited understanding of the |
|
realm::_impl::ExternalCommitHelper::listen() I started seeing this on Crashlytics just a few days ago, with a new release of my app to the AppStore. Not using Realm any differently than before. Looks like iPhone 5 and iOS 10.x are affected. |
|
A thread sitting in mach_msg_trap inside a call to realm::_impl::ExternalCommitHelper::listen() just means that our worker thread is currently waiting for work, and does not indicate that the crash was there. If the crash report includes |
|
I spent more time on this one and looks like it might not be related to Realm at all. After reproducing this crash few more times I got very different stacktraces and sometimes Crashlytics reports point to different places in code, like CFNetwork and other. One thing that all crash reports have in common is a very low amount of memory available (less than 10mb in all cases). Also, by the look of this thread the crash seems to be reproducible mostly on devices with 32-bit architecture(as people mentioned, its mostly iOS versions less than 11 and devices like iPhone 5c, iPad Mini, iPod Touch 5G, etc). I added more logs to my code which is being executed when the crash is happening and found out that it happens exactly when I create a view model for a new controller and it never even reaches the first line of code in I always get MARKER1 in crash reports, but never MARKER2, so one can assume it has something to do with memory allocation in release builds... |
|
This appears to be an issue with Apple 32-bit devices using Xcode 11.4 and swift 5.2 Having the same issue and recompiling the application using Xcode 11.5 resolved the realm crash. |
|
Can confirm, my app no longer crashes when built by Xcode 11.5. |
thank you @victordupreez its works for me too |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Goals
Should not abort the app.
Expected Results
Realm instance should be created properly.
Actual Results
App getting crash on REALM library
realm::_impl::ExternalCommitHelper::listen() (external_commit_helper.cpp:217)
Steps to Reproduce
Not sure
Code Sample
Not Applicable. Generally while creating realm instances.
Version of Realm and Tooling
Realm framework version: 'RealmSwift', '~> 3.14.1'
Realm Object Server version:
Xcode version: 10.1 (10B61)
iOS version: 10.3.3 and above all.
Dependency manager + version: Cocoapod
The text was updated successfully, but these errors were encountered: