I found the bug database at code.google.com, but I cannot find your bug report.
FYI: I think we've found a work-around. We're using GL to copy to the screen
and that seems much more stable (and a little faster). If it would help, I can
send you the modified version of the test program that
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
Thanks, I've filed a bug.
On Tue, Aug 2, 2011 at 10:45 AM, Joshua Smith joshuaesm...@charter.netwrote:
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
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?
6 matches
Mail list logo
