Yes, that's what just did in a dev build, will see it helps. Curiously enough, the framework's SQLiteQueryBuilder uses a StringBuilder that is initially 120 chars long, and the corruption happens at 112'th character.
I've long anticipated an Android device with firmware that calculates 2+2 as 5... this is not quite it, but comes pretty close. -- K 2013/9/29 Piren <[email protected]> > never came across such a report, but if it's isolated to that specific > query maybe try replacing it with a rawQuery instead and see if it makes a > difference. > > > On Sunday, September 29, 2013 1:05:26 AM UTC+3, Kostya Vasilyev wrote: >> >> Hello, >> >> One of my users reports a crash like this: >> >> android.database.sqlite.**SQLiteException: no such column: _id (code 1): , >> while compiling: SELECT _id, generation, flags, numeric_uid, body_main_size, >> body_main_fetched_size, body_alt_size, body_alt_fetc¤ , search_token, >> op_flags, op_move_to_folder, op_hide, misc_flags FROM message WHERE >> folder_id = ? AND numeric_uid >= ? AND numeric_uid < ? >> at >> android.database.sqlite.**SQLiteConnection.**nativePrepareStatement(Native >> Method) >> at >> android.database.sqlite.**SQLiteConnection.**acquirePreparedStatement(**SQLiteConnection.java:886) >> at >> android.database.sqlite.**SQLiteConnection.**executeForCursorWindow(**SQLiteConnection.java:835) >> at >> android.database.sqlite.**SQLiteSession.**executeForCursorWindow(**SQLiteSession.java:836) >> at >> android.database.sqlite.**SQLiteQuery.fillWindow(**SQLiteQuery.java:62) >> at >> android.database.sqlite.**SQLiteCursor.fillWindow(**SQLiteCursor.java:158) >> at >> android.database.sqlite.**SQLiteCursor.getCount(**SQLiteCursor.java:148) >> at >> android.database.**AbstractCursor.moveToPosition(**AbstractCursor.java:197) >> at >> android.database.**AbstractCursor.moveToNext(**AbstractCursor.java:245) >> at <my code here> >> >> Note the weird character in the middle of: >> >> "body_alt_fetc >>right here>>¤<<<<< , search_token". >> >> There are supposed to be a few more characters where this weird one is. >> >> My code here calls SQLiteDatabase.query with a String[] projection, a >> table name, a simple selection and its arguments, etc. All very basic stuff. >> >> The crash happens "once in a while", even though this query runs >> literally all the time. It's always this query, too, even though there are >> dozens more, for same table, and in same source file. >> >> It looks to me like a memory overwrite, presumably in native code ('cause >> it's pretty hard to overwrite something by accident on the Java side of >> things). >> >> Has anyone ran into this or a similar query corruption? >> >> The device is a Zopo 980, if that means anything. >> >> Thanks, >> -- K >> >> >> -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Android Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
