that *doesn't* crash.
On Aug 3, 2011, at 10:08 AM, Joshua Smith wrote:
Do you do public tracking of the bug database, so I can keep an eye on this?
On Aug 3, 2011, at 1:16 AM, Dianne Hackborn wrote:
Thanks, I've filed a bug.
On Tue, Aug 2, 2011 at 10:45 AM, Joshua Smith joshuaesm...@charter.net
Do you do public tracking of the bug database, so I can keep an eye on this?
On Aug 3, 2011, at 1:16 AM, Dianne Hackborn wrote:
Thanks, I've filed a bug.
On Tue, Aug 2, 2011 at 10:45 AM, Joshua Smith joshuaesm...@charter.net
wrote:
Update: We've created a small reproducible test case
Update: We've created a small reproducible test case. Run this code for an
hour (usually less) on a XOOM with 3.2 and you will reboot.
We haven't gotten lucky enough to get a log, so we cannot be absolutely certain
that this reboot is the same one we're hitting, but it probably is.
Who do I
Reboot. Uptime reported 30 seconds up when we reconnected.
On Jul 28, 2011, at 1:02 PM, Chris Stratton wrote:
On Thursday, July 28, 2011 11:21:18 AM UTC-4, Joshua Smith wrote:
Our app, which works fine in 3.1 and earlier, has started experiencing
a hard crash that cause our XOOM to reboot
Our app, which works fine in 3.1 and earlier, has started experiencing
a hard crash that cause our XOOM to reboot. Usually, when this
happens, the logs disappear, but in a couple of cases, we've managed
to catch the exception. Anybody have a clue what these logs might be
trying to tell us?
We're getting an app ready for Android, and we've just hit a complete
show-stopper with the 3.2 update.
Our app runs for about a minute, and then the XOOM just reboots. There
is absolutely no evidence that we can find in any log as to what the
problem is. The same app is running just fine in 3.1
6 matches
Mail list logo
