Slowing down the monkey causes this exception to go away. There is probably a race condition inside SQLite - a condition that is never going to come up in realistic user situations but only under heavy synthetic loads. Still, it should probably be studied and fixed, just to prevent the rare case where it does happen.
-- 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
