-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Strange log message: "N5realm10LogicErrorE: Bad version number" #4422
Comments
Thanks for reporting this. Could you share a complete stack trace the next time this happens? We won't be able to do anything until we have more steps. |
There is actually no crash just randomly seeing it in our logs |
Hmm, since that's an exception being thrown, it should crash your app, unless you're catching exceptions, which isn't something I'd advise... Unless I'm missing more context here. I don't think we ever translate this specific exception to an |
I have just experience the same thing after update carthage dependencies. I opens the debugger in the following file "group_shared.hpp" at line 911 in method I am saving an object which i have in a Result where i listen to changesets
Here is my cart file
when updating carthage dependencies i also get this strange warning
|
I'm having the same issue when launching my app.
No crash and everything is working fine. It seems to only appear once in the log. |
Sounds like I'm not the only one |
Can anyone here actually share steps to reproduce? Seems like this might happen if you're calling |
Not calling realm.refresh() anywhere in our project. Ill set a symbolic break point and see if I can catch it |
Here the exception stack using
As said in #4428, we don't have the steps to reproduce it, but once that exception has been fired the interface will freeze (dead lock in the |
Managed to get a stack in Simulator (iOS 10.2 / Realm(Swift) 2.1.1 / XCode 8.2). I can't find any pattern that would triggers the exception.
|
Same here; I've just encountered this as well in tvOS / Xcode 8.2 / Swift (Cocoapods dependency manager). I was Googling for hints and found this issue :)
|
We'd love to address this, but to make progress we'll likely need a sample project that reproduces this issue. Can anyone who's experienced this provide us with steps to trigger? |
I have faced this same problem when i update my carthage file: carthage update --toolchain com.apple.dt.toolchain.Swift_2_3 --no-use-binaries --platform iOS My cart file contains: github "realm/realm-cocoa" I got uncaught exception in "group_shared.hpp" file.
I throws this exception : LogicError(LogicError::bad_version) |
@kirtiparghi can you share a project that triggers this? What you shared is a way to install Realm, which we're familiar with already, and is not at fault here. |
Just a quick ping of this issue. If anyone can provide us with a project that triggers this issue, that would be much appreciated. Thanks a lot! :) Happy holidays! |
Hullo Tim and team, I'm seeing this intermittently with the It seems to happen more often if I take out the NSLog statements... I added the
That code is running on thread 1. The exception is occurring in The
|
I encounter this bug using my app with realm 1.0.2 right after I update Realm up to 2.1.1. It causes db update listener to break. UPD: according to our testers, it breaks even on pure 2.1.1 (without any updating from 1.0.2 to 2.1.1) |
I'm having the same issue, realm version: 2.1.1 |
First I got a -[__NSArrayM insertObject:atIndex:]: object cannot be nil error then I set an exception breakpoint to try to get this error again but instead I keep getting this N5realm10LogicErrorE: Bad version number exception. Edit: On further investigation, I see that the the array problem is unrelated. |
Ok, I came across this issue as I was trying to figure out why my Realm file was ballooning to over a gigabyte sometimes. Here is where I am at:
I was running into these problems:
Here is the stack trace from that exception: * thread #9: tid = 0xec9dd, 0x0000000183162efc libc++abi.dylib`__cxa_throw, name = 'RLMRealm notification listener', stop reason = breakpoint 1.2
frame #0: 0x0000000183162efc libc++abi.dylib`__cxa_throw
* frame #1: 0x00000001007c1f50 Realm`void realm::SharedGroup::advance_read<(anonymous namespace)::TransactLogValidator>(this=0x000000010208be00, observer=0x000000016e26c960, version_id=(version = 8884, index = 16))::TransactLogValidator*, realm::VersionID) + 220 at group_shared.hpp:915
frame #2: 0x00000001007c1e68 Realm`void realm::_impl::SharedGroupFriend::advance_read<(anonymous namespace)::TransactLogValidator>(sg=0x000000010208be00, obs=0x000000016e26c960, ver=(version = 8884, index = 16))::TransactLogValidator*, realm::VersionID) + 64 at group_shared.hpp:1086
frame #3: 0x00000001007c1e1c Realm`void realm::LangBindHelper::advance_read<(anonymous namespace)::TransactLogValidator>(sg=0x000000010208be00, observer=0x000000016e26c960, version=(version = 8884, index = 16))::TransactLogValidator&&, realm::VersionID) + 64 at lang_bind_helper.hpp:335
frame #4: 0x00000001007c1878 Realm`auto realm::_impl::transaction::advance(this=0x000000016e26cd80, args=0x000000016e26c960)::$_0::operator()<(anonymous namespace)::TransactLogValidator>((anonymous namespace)::TransactLogValidator&&) const + 72 at transact_log_handler.cpp:823
frame #5: 0x00000001007c138c Realm`(anonymous namespace)::TransactLogObserver::TransactLogObserver<realm::_impl::transaction::advance(this=0x000000016e26cd90, context=0x0000000000000000, sg=0x000000010208be00, func=0x000000016e26cd80, schema_mode=<unavailable>, notifiers=0x000000016e26ce08)::$_0>(realm::BindingContext*, realm::SharedGroup&, realm::_impl::transaction::advance(realm::SharedGroup&, realm::BindingContext*, realm::SchemaMode, realm::VersionID)::$_0&&, realm::util::Optional<realm::SchemaMode>, realm::_impl::NotifierPackage&) + 672 at transact_log_handler.cpp:274
frame #6: 0x00000001007bb1f0 Realm`(anonymous namespace)::TransactLogObserver::TransactLogObserver<realm::_impl::transaction::advance(this=0x000000016e26cd90, context=0x0000000000000000, sg=0x000000010208be00, func=0x000000016e26cd80, schema_mode=<unavailable>, notifiers=0x000000016e26ce08)::$_0>(realm::BindingContext*, realm::SharedGroup&, realm::_impl::transaction::advance(realm::SharedGroup&, realm::BindingContext*, realm::SchemaMode, realm::VersionID)::$_0&&, realm::util::Optional<realm::SchemaMode>, realm::_impl::NotifierPackage&) + 60 at transact_log_handler.cpp:262
frame #7: 0x00000001007bb124 Realm`realm::_impl::transaction::advance(sg=0x000000010208be00, context=0x0000000000000000, schema_mode=ResetFile, version=(version = 8884, index = 16)) + 140 at transact_log_handler.cpp:822
frame #8: 0x00000001005e8e60 Realm`(anonymous namespace)::IncrementalChangeInfo::advance_to_final(this=0x000000016e26d700, version=(version = 8884, index = 16)) + 116 at realm_coordinator.cpp:468
frame #9: 0x00000001005e78c4 Realm`realm::_impl::RealmCoordinator::run_async_notifiers(this=0x0000000101e4d9b8) + 4668 at realm_coordinator.cpp:587
frame #10: 0x00000001005e6498 Realm`realm::_impl::RealmCoordinator::on_change(this=0x0000000101e4d9b8) + 40 at realm_coordinator.cpp:410
frame #11: 0x00000001005992bc Realm`realm::_impl::ExternalCommitHelper::listen(this=0x0000000101e4a020) + 648 at external_commit_helper.cpp:217
frame #12: 0x000000010059d54c Realm`realm::_impl::ExternalCommitHelper::ExternalCommitHelper(this=0x0000000101e4c2e0)::$_0::operator()() const + 24 at external_commit_helper.cpp:159
frame #13: 0x000000010059d528 Realm`_ZNSt3__112__async_funcIZN5realm5_impl20ExternalCommitHelperC1ERNS2_16RealmCoordinatorEE3$_0JEE9__executeIJEEEvNS_15__tuple_indicesIJXspT_EEEE [inlined] std::__1::__invoke<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0>(__f=0x0000000101e4c2e0)::$_0>(fp)(std::__1::forward<>(fp0))), realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0&&) + 64 at __functional_base:416
frame #14: 0x000000010059d518 Realm`_ZNSt3__112__async_funcIZN5realm5_impl20ExternalCommitHelperC1ERNS2_16RealmCoordinatorEE3$_0JEE9__executeIJEEEvNS_15__tuple_indicesIJXspT_EEEE(this=0x0000000101e4c2e0, (null)=__tuple_indices<> @ 0x000000016e26ec10) + 48 at future:2348
frame #15: 0x000000010059d4dc Realm`std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0>::operator(this=0x0000000101e4c2e0)() + 24 at future:2341
frame #16: 0x000000010059d3ec Realm`std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::__execute(this=0x0000000101e4c250) + 32 at future:1031
frame #17: 0x000000010059dc70 Realm`std::__1::__thread_proxy<std::__1::tuple<void (std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::*)(), std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >*> >(void*, void*) [inlined] std::__1::__invoke<void (std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::*)(), std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >*, void>(__f=0x0000000101e50ad0, __a0=0x0000000101e50ae0)::$_0> >*>(fp0)).*fp(std::__1::forward<>(fp1))), void (std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::*&&)(), std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >*&&) + 100 at __functional_base:383
frame #18: 0x000000010059dc0c Realm`std::__1::__thread_proxy<std::__1::tuple<void (std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::*)(), std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >*> >(void*, void*) [inlined] _ZNSt3__116__thread_executeIMNS_19__async_assoc_stateIvNS_12__async_funcIZN5realm5_impl20ExternalCommitHelperC1ERNS4_16RealmCoordinatorEE3$_0JEEEEEFvvEJPSA_EJLm1EEEEvRNS_5tupleIJT_DpT0_EEENS_15__tuple_indicesIJXspT1_EEEE(__t=0x0000000101e50ad0) + 40 at thread:347
frame #19: 0x000000010059dbe4 Realm`std::__1::__thread_proxy<std::__1::tuple<void (std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >::*)(), std::__1::__async_assoc_state<void, std::__1::__async_func<realm::_impl::ExternalCommitHelper::ExternalCommitHelper(realm::_impl::RealmCoordinator&)::$_0> >*> >(__vp=0x0000000101e50ad0) + 248 at thread:357
frame #20: 0x00000001837d1850 libsystem_pthread.dylib`_pthread_body + 240
frame #21: 0x00000001837d1760 libsystem_pthread.dylib`_pthread_start + 284
frame #22: 0x00000001837ced94 libsystem_pthread.dylib`thread_start + 4 I can't share my code where this error is currently happening. I did make an example project that uses my Configuration object to make and manage my the That project is clonable/downloadable here. Just run good old I was not able to get this demo project to throw the "N5realm10LogicErrorE: Bad version number" error. If I do, I will post an edit with my steps. This project does demonstrate the ballooning of my Check out my demo app and let me know if I am using Also, if my ballooning issue warrants its own issue let me know and I will move it/file it appropriately. Hopefully, I am just miss using something or not understanding this. |
This should be fixed by realm/realm-object-store#355. |
Realm v2.4.0 seems to fix that warning for me. |
v2.4.0 Fixed this for me also. |
Again getting this issue in |
@Ankit-Aggarwal please file a new issue taking care to fill out the template with as much relevant information as possible. Thanks. |
Seeing the following in our logs randomly
uncaught exception in notifier thread: N5realm10LogicErrorE: Bad version number
Unfortunately, don't have any specific steps to reproduce. Doesn't seem to be causing any issues but thought I would let you guys know
Realm version: 2.1.1
Xcode version: 8.2 beta 2
iOS/OSX version: 10.1
Dependency manager + version: Carthage 18.1
The text was updated successfully, but these errors were encountered: