Skip to content
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

[RLMRealm commitWriteTransactionWithoutNotifying:error:] #6189

Closed
huuchi207 opened this issue Jan 11, 2023 · 2 comments
Closed

[RLMRealm commitWriteTransactionWithoutNotifying:error:] #6189

huuchi207 opened this issue Jan 11, 2023 · 2 comments
Assignees
Labels
O-Community Waiting-For-Reporter Waiting for more information from the reporter before we can proceed

Comments

@huuchi207
Copy link

SDK and version

SDK : Cocoa (Cocoa, Java, etc)
Version: 10.14.0

Observations

  • How frequent do the crash occur? Answer: Sometime
  • Does it happen in production or during dev/test? Answer: Production
  • Can the crash be reproduced by you? Answer: No
  • Can you provide instructions for how we can reproduce it? Answer: I can not. I see the problem in Firebase Crashlytic

Crash log / stacktrace

Crashed: com.apple.main-thread
0 libsystem_kernel.dylib 0x7b38 __pthread_kill + 8
1 libsystem_pthread.dylib 0x73bc pthread_kill + 268
2 libsystem_c.dylib 0x20524 abort + 168
3 Realm 0x3045f4 please_report_this_issue_in_github_realm_realm_core + 10
4 Realm 0x3048f4 realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits, std::__1::allocator >&) + 328
5 Realm 0x304c58 realm::util::terminate_with_info(char const*, char const*, long, char const*, std::initializer_listrealm::util::Printable&&) + 388
6 Realm 0x1b9270 void realm::util::terminate_with_info<unsigned long const&, unsigned long long const&, unsigned long&, unsigned long&, unsigned long long&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >(char const*, int, char const*, char const*, unsigned long const&, unsigned long long const&, unsigned long&, unsigned long&, unsigned long long&, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >&&) + 146
7 Realm 0x1b8ca4 realm::GroupWriter::recreate_freelist(unsigned long) + 1960
8 Realm 0x1b77e0 realm::GroupWriter::write_group() + 688
9 Realm 0x197fbc realm::DB::low_level_commit(unsigned long long, realm::Transaction&) + 380
10 Realm 0x197dd0 realm::DB::do_commit(realm::Transaction&) + 112
11 Realm 0x1983a4 realm::Transaction::commit_and_continue_as_read() + 80
12 Realm 0x3c53c0 realm::_impl::RealmCoordinator::commit_write(realm::Realm&) + 100
13 Realm 0x451e98 realm::Realm::commit_transaction() + 196
14 Realm 0x13429c -[RLMRealm commitWriteTransactionWithoutNotifying:error:] + 288
15 RealmSwift 0x5e4f4 $s10RealmSwift0A0V5write16withoutNotifying_xSaySo20RLMNotificationTokenCG_xyKXEtKlF + 400

Steps & Code to Reproduce

@nicola-cab
Copy link
Member

nicola-cab commented Jan 11, 2023

Hello, thanks for reporting this. This issue seems a duplicate of this one #6071.. Essentially, we have a problem while we are reclaiming some memory. However, you are using a very old version of realm-core (11.x) which was effected by a corruption bug, this error can be caused by that.
If the database is corrupted, you will need to delete it and recreate from scratch. You will need also to upload some SDK version that is targeting core >=12.12.
If you can share the database file with me, I can have a look and try to understand if it got corrupted.

@sync-by-unito sync-by-unito bot added the Waiting-For-Reporter Waiting for more information from the reporter before we can proceed label Jan 11, 2023
@sync-by-unito sync-by-unito bot closed this as completed Feb 7, 2023
@kiburtse
Copy link
Contributor

kiburtse commented Feb 7, 2023

Duplicate of #6071

@kiburtse kiburtse marked this as a duplicate of #6071 Feb 7, 2023
@kiburtse kiburtse closed this as not planned Won't fix, can't repro, duplicate, stale Oct 11, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
O-Community Waiting-For-Reporter Waiting for more information from the reporter before we can proceed
Projects
None yet
Development

No branches or pull requests

3 participants