wordpress-mobile / wordpress-mobile/WordPress-Android
sqlite3_sourceid
Open
Nobody has claimed this yet.
[Pri] High
[Type] Crash
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Sentry Issue: JETPACK-ANDROID-2X
SIGSEGV: Segfault
?, in sqlite3_sourceid
?, in sqlite3_backup_step
?, in sqlite3_sourceid
?, in sqlite3_step
?, in android::register_android_database_SQLiteConnection
...
(2 additional frame(s) were not displayed)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Sentry trace for issue JETPACK-ANDROID-2X and inspect the Android SQLite integration around register_android_database_SQLiteConnection, sqlite3_step, sqlite3_backup_step, and sqlite3_sourceid. Determine whether the SIGSEGV can be reproduced or traced to a specific integration path; done means identifying and fixing the crash with a regression test or documenting why it cannot be reproduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, sqlite
- Domain
- databases, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100