SQLiteBlobTooBigException: Row too big to fit into CursorWindow requiredPos=0, totalRows=1

sentry-io[bot] commented 10 months ago

SQLiteBlobTooBigException: Row too big to fit into CursorWindow requiredPos=0, totalRows=1
    at android.database.sqlite.SQLiteConnection.nativeExecuteForCursorWindow(SQLiteConnection.java)
    at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:942)
    at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:838)
    at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
    at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:153)
...
(23 additional frame(s) were not displayed)

By July 3rd, 2023, this issue has impacted 4 users. Seems it was recently introduced as it's first seen in version 22.5.

sentry-io[bot] commented 10 months ago

Sentry issue: JETPACK-ANDROID-7YW

fluiddot commented 10 months ago

Marking issue as low priority since it's affecting a small percentage of users. So far, only 0.003% of 22.6 users are affected.

thomashorta commented 10 months ago

I found a few other sentry crashes with similar stacktrace (will link them to this issue), some when accessing Stats, other when accessing Posts, but overall the same issue with the CursorWindow. Doing some investigation, I found this was already a problem in the past (#13273) and there were a few attempted fixes here and here.

Those attempts try to increase the CursorWindow size to hopefully fit the rows when accessing the SQLite tables, but both of them made the changes on the WellSqlConfig that is used only in debug builds, so none of those fixes ever reached our users in release builds.

I will bump the priority to medium because this is a crash happening to a low percentage of users and I would suggest implementing the CursorWindow size increase in the release build of the app as well, maybe starting again at 5mb, like WooCommerce, so we can measure if the SQLiteBlobTooBigException numbers decrease.

Note: the actual underlying issue is that we might have SQL tables with rows storing too much data (a long post for instance). In most cases, there's nothing we can do other than try to increase the window size, but there are some cases that it might make sense to do a deeper analysis in the future, for example: the Stats are all saved in the StatsBlock and the data is a json blob instead of having separate fields/tables for each Stat field/type.

sentry-io[bot] commented 10 months ago

Sentry issue: JETPACK-ANDROID-96J

sentry-io[bot] commented 10 months ago

Sentry issue: JETPACK-ANDROID-803

sentry-io[bot] commented 10 months ago

Sentry issue: JETPACK-ANDROID-9EK

sentry-io[bot] commented 10 months ago

Sentry issue: JETPACK-ANDROID-9EM

sentry-io[bot] commented 10 months ago

Sentry issue: JETPACK-ANDROID-87K

sentry-io[bot] commented 10 months ago

Sentry issue: JETPACK-ANDROID-81E