I\'m working on an Android app which is now in production, and am occasionally seeing exceptions (reported via airbrake) with stuff like this:
[1.0.4] java.l
I never did track down the exact cause of this problem, but based on my experience developing the app in question I believe it was caused by hitting the memory limit for the activity. After your activity runs out of memory, it seems that all sorts of strange errors can happen, including stuff like this.
When I made other improvements to the app's memory management (particularly by using SoftReference
with Bitmaps), these type of exceptions starting appearing less frequently.