-
Notifications
You must be signed in to change notification settings - Fork 171
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
Startup crash #5344
Comments
@michalrentka Thank you for filling this issue. We are looking into it. |
@ironage There seems to be a problem when reading the schema version from the metadata table (although open_db succeeds). Could you please have a look at this? |
It is a shame we don't have the std::cerr output from this report. I assume from the stack trace that the cookie check fails. I wonder if there be a race on the allocator's |
@ironage no, I always open a new realm when I work with database. So each thread should have separate realms. To explain a bit how I work with Realm, I made this simple wrapper to access the database: https://github.com/zotero/zotero-ios/blob/master/Zotero/Controllers/Database/RealmDbStorage.swift The app has a single Also, this crash happened after app launch (https://github.com/zotero/zotero-ios/blob/6eedfef089276fbe8aa2d16690eeb49885873c0c/Zotero/Controllers/Controllers.swift#L383) when I try to create a shared This is a fresh app start where the only access is made to read schema version from main thread from |
Closed by #5993 |
SDK and version
SDK : Cocoa
Version: 10.23.0
Observations
A user reported crashing on each startup. It was an existing user who probably recently updated the app, so it could be a migration issue. I can't reproduce it myself. The stack trace said to share the crash log.
Crash log / stacktrace
Steps & Code to Reproduce
From the crash report it looks like it's crashing when trying to read a schema version:
https://github.com/zotero/zotero-ios/blob/ea44d2c74a7b115d3f88d61c781f3daccfd7aa1e/Zotero/Models/Database/Database.swift#L36.
It's not really needed at this point, so if I shouldn't read schema version before Realm is initialised, I'll get rid of it.
The text was updated successfully, but these errors were encountered: