Closed kharmabum closed 7 years ago
Hi @kharmabum. Thanks for reaching out. Would you be able to provide us with a sample project demonstrating the issue and any other information you can provide? From there, we'll be able to get one of our engineers to look into this.
Just bringing attention back to this issue. @kharmabum: Would you be able to provide us with a sample project demonstrating the issue and any other information you can provide? From there, we'll be able to get one of our engineers to look into this. Thanks.
Just bringing attention back to this issue. @kharmabum: Would you be able to provide us with a sample project demonstrating the issue and any other information you can provide? From there, we'll be able to get one of our engineers to look into this. Thanks.
Hey @kharmabum, what makes you think the crash is happening inside RLMClassInfo::propertyForTableColumn()
? The screenshot you posted doesn't appear to indicate an exception being thrown or null pointer being dereferenced, or anything else indicating that that function is crashing...
Perhaps another thread was the culprit and you misattributed the main thread as the source of the crash?
In any case, we can't move on this until we get more information from you, as @istx25 has requested.
In the future, invoking bt
from the lldb console is much better than screenshots: it can help us textually search for similar issues and will include information that you may have otherwise omitted, which is likely the case here.
Sorry for the delay in responses. I've been low on bandwidth the past few weeks.
@jpsim will do in the future, here are a few full stack traces courtesy of sentry: https://gist.github.com/kharmabum/feb5b3a8e7fe405faede857157ca76f6
@kharmabum thanks for sharing that. I'm re-including it here so it can come up when we search for similar stack traces in the future:
@kharmabum could you please post the full model definitions that are being observed? If you could also share the notification block code, that'd be helpful.
Hi @kharmabum. Just echoing @jpsim's request. Would you please post the full model definitions that are being observed? As well as the notification block code too (if possible). Thanks!
@kharmabum are you still seeing this with the current master
branch? Thanks!
@jpsim I have not. Both this crash and another crash I reported via email (trace included below) have ceased since I made a few changes:
(1) Avoid frequently removing and immediately re-adding a KVO observer (I was doing this a lot) (2) Instead of deleting all objects in a realm (this is usually the point at which the crash would surface) I am deleting the entire realm file
Even if I removed all observers prior to deleting all objects I would encounter this crash.
Stack trace for the other possibly relevant crash:
/Users/realm/workspace/create_github_release_cocoa/realm-cocoa/Realm/ObjectStore/src/impl/transact_log_handler.cpp:147: [realm-core-2.3.0] Assertion failed: list.col < list.observer->changes.size()
0 Realm 0x0000000103b68898 _ZN5realm4utilL18terminate_internalERNSt3__118basic_stringstreamIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE + 40
1 Realm 0x0000000103b68b9a _ZN5realm4util9terminateEPKcS2_lOSt16initializer_listINS0_9PrintableEE + 506
2 Realm 0x0000000103af3d7c _ZN12_GLOBAL__N_122KVOTransactLogObserver14parse_completeEv + 1512
3 Realm 0x0000000103af2ab6 _ZN5realm11SharedGroup15do_advance_readIN12_GLOBAL__N_122KVOTransactLogObserverEEEbPT_NS_9VersionIDERNS_5_impl7HistoryE + 388
4 Realm 0x0000000103ae97ba _ZN5realm5_impl11transaction7advanceERNS_11SharedGroupEPNS_14BindingContextERNS0_15NotifierPackageE + 422
5 Realm 0x0000000103a1a005 _ZN5realm5_impl16RealmCoordinator16advance_to_readyERNS_5RealmE + 271
6 Realm 0x0000000103ae5e4f _ZN5realm5Realm6notifyEv + 189
7 Realm 0x0000000103af8653 _ZNK5realm5_impl17WeakRealmNotifier8CallbackclEv + 45
8 CoreFoundation 0x0000000106fd0761 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
9 CoreFoundation 0x0000000106fb598c __CFRunLoopDoSources0 + 556
10 CoreFoundation 0x0000000106fb4e76 __CFRunLoopRun + 918
11 CoreFoundation 0x0000000106fb4884 CFRunLoopRunSpecific + 420
12 GraphicsServices 0x000000010b835a6f GSEventRunModal + 161
13 UIKit 0x0000000104993c68 UIApplicationMain + 159
14 Other Chat 0x0000000100f346df main + 111
15 libdyld.dylib 0x000000010c1b068d start + 1
16 ??? 0x0000000000000001 0x0 + 1
IMPORTANT: if you see this error, please send this log to help@realm.io
That last stack trace could be relevant. We appear to be tracking a similar crash in #4694. Any chance you can share more about that? Thanks!
@jpsim looking around, can't find anything, but will keep an eye out.
Hi @kharmabum! I'm just doing a pass of some of our older issues and am wondering if it's worth closing this issue at this point. Have you seen anything since your last post?
Feel free to close. Will reopen if I see it again.
Realm version: v2.2.0 Xcode version: 8.2.1 iOS/OSX version: 10.3