Closed chrisboyle closed 14 years ago
Well this is now up to 27 reports, and I'm not really any closer to solving it. There being two frames and it being a SIGSEGV/SIGBUS suggests dvmCreateCstrFromString()
as the innermost frame and j
(that is, the return from CallObjectMethod(...,getText,...)
) being invalid. No closer to knowing why, except that I probably fail at thread safety somehow.
No reports of this in 8853.1 or newer. I think commit 9750c6836dda2e1ad00a7299ca6ce9b05072eee1, comit 131bfbbd4be1d21702f878de627a68f1f66515b7, commit 92f474dcb09f4cdd228e5bfd95b8333b5fc46cd5 may actually have helped! :-) Closing, to be reopened on further crash reports.
Since the release of 8750.5 I have had 9 crash reports in the same place (and one other unrelated). Seen on 1.5, 1.6 and 2.0, on a range of devices. The traces all decode like this:
Here is an extract from a typical report (from a Sprint Hero on 1.5), with frame 03 annotated:
This means we were starting a game (either resuming it because the app was started, or New Game was pressed, or a custom game was started; it doesn't matter, there have been reports from all these cases) and we finished android_deserialise, continued on to fill in the "Type" menu, and on trying to call from C up to Java to translate the first item for that menu, we crashed somewhere in the mechanics of GetStringUTFChars. Perhaps either env or j was invalid.
There have been over 3000 downloads on Android Market since this release went out, and only these 9 reports, so even allowing for under-reporting, this suggests that this issue is rare. Perhaps a threading issue or some such.