Re: [android-developers] Hard Crash (Reboot) in 3.2
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 *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 wrote: 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 send this to? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Hard Crash (Reboot) in 3.2
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. 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 send this to? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Hard Crash (Reboot) in 3.2
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 send this to? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en CrashSurfaceFlinger.java Description: Binary data
Re: [android-developers] Hard Crash (Reboot) in 3.2
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 cannot be absolutely certain that this reboot is the same one we're hitting, but it probably is. Who do I send this to? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Hard Crash (Reboot) in 3.2
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. Kernel reboot, or android runtime restart? You can tell the difference soon thereafter from cat /proc/uptime or (if present) the uptime command at the adb shell -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Hard Crash (Reboot) in 3.2
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? Crash 1: 07-21 16:52:29.050: INFO/dalvikvm(730): Jit: resizing JitTable from 4096 to 8192 07-21 16:59:26.740: INFO/DEBUG(85): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 07-21 16:59:26.740: INFO/DEBUG(85): Build fingerprint: 'motorola/ tervigon/wingray:3.2/HTJ85B/140714:user/release-keys' 07-21 16:59:26.740: INFO/DEBUG(85): pid: 144, tid: 264 system_server 07-21 16:59:26.740: INFO/DEBUG(85): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr afa0be00 07-21 16:59:26.740: INFO/DEBUG(85): r0 0050 r1 0014 r2 0001 r3 0022c298 07-21 16:59:26.740: INFO/DEBUG(85): r4 0022c298 r5 r6 0001 r7 0001 07-21 16:59:26.740: INFO/DEBUG(85): r8 0001 r9 0022c264 10 a7d45252 fp 0096 07-21 16:59:26.740: INFO/DEBUG(85): ip a7d47f44 sp 5bff98c8 lr a7d3ced3 pc afa0be00 cpsr 0010 07-21 16:59:26.740: INFO/DEBUG(85): d0 3f003f80 d1 3ff0 07-21 16:59:26.740: INFO/DEBUG(85): d2 3ff0 d3 4085e000 07-21 16:59:26.740: INFO/DEBUG(85): d4 401c d5 4059 07-21 16:59:26.740: INFO/DEBUG(85): d6 43e0 d7 3f803f80 07-21 16:59:26.740: INFO/DEBUG(85): d8 d9 07-21 16:59:26.740: INFO/DEBUG(85): d10 d11 07-21 16:59:26.740: INFO/DEBUG(85): d12 d13 07-21 16:59:26.740: INFO/DEBUG(85): d14 d15 07-21 16:59:26.740: INFO/DEBUG(85): scr 2012 07-21 16:59:26.920: INFO/DEBUG(85): #00 pc afa0be00 07-21 16:59:26.920: INFO/DEBUG(85): #01 pc 0001ded0 /system/ lib/libutils.so (_ZNK7android10VectorImpl8capacityEv) 07-21 16:59:26.920: INFO/DEBUG(85): #02 pc 0001e1fc /system/ lib/libutils.so (_ZN7android10VectorImpl5_growEjj) 07-21 16:59:26.920: INFO/DEBUG(85): #03 pc 0001e2de /system/ lib/libutils.so (_ZN7android10VectorImpl8insertAtEPKvjj) 07-21 16:59:26.920: INFO/DEBUG(85): #04 pc 0001e316 /system/ lib/libutils.so (_ZN7android10VectorImpl3addEPKv) 07-21 16:59:26.920: INFO/DEBUG(85): #05 pc 0002240a /system/ lib/libutils.so (_ZN7android6Looper12pushResponseEiRKNS0_7RequestE) 07-21 16:59:26.920: INFO/DEBUG(85): #06 pc 000226b6 /system/ lib/libutils.so (_ZN7android6Looper9pollInnerEi) 07-21 16:59:26.920: INFO/DEBUG(85): #07 pc 00022822 /system/ lib/libutils.so (_ZN7android6Looper8pollOnceEiPiS1_PPv) 07-21 16:59:26.930: INFO/DEBUG(85): #08 pc c19c /system/ lib/libgui.so (_ZNK7android16SensorEventQueue12waitForEventEv) 07-21 16:59:26.930: INFO/DEBUG(85): #09 pc 00063d00 /system/ lib/libandroid_runtime.so 07-21 16:59:26.930: INFO/DEBUG(85): libc base address: afc1f000 07-21 16:59:26.930: INFO/DEBUG(85): code around pc: 07-21 16:59:26.930: INFO/DEBUG(85): afa0bde0 07-21 16:59:26.930: INFO/DEBUG(85): afa0bdf0 07-21 16:59:26.930: INFO/DEBUG(85): afa0be00 07-21 16:59:26.930: INFO/DEBUG(85): afa0be10 07-21 16:59:26.930: INFO/DEBUG(85): afa0be20 07-21 16:59:26.930: INFO/DEBUG(85): code around lr: 07-21 16:59:26.930: INFO/DEBUG(85): a7d3ceb0 60046083 bf00bd10 af7e ffc8 07-21 16:59:26.930: INFO/DEBUG(85): a7d3cec0 4603b510 b1206840 0c0cf850 f7f36919 07-21 16:59:26.930: INFO/DEBUG(85): a7d3ced0 bd10e9f4 4790b510 bf00bd10 b90b6843 07-21 16:59:26.930: INFO/DEBUG(85): a7d3cee0 e0024618 fb006900 47703001 b51068c3 07-21 16:59:26.930: INFO/DEBUG(85): a7d3cef0 d402079b 68db6803 bd104798 4c05b570 07-21 16:59:26.930: INFO/DEBUG(85): stack: 07-21 16:59:26.930: INFO/DEBUG(85): 5bff9888 a7d450b0 /system/ lib/libutils.so 07-21 16:59:26.930: INFO/DEBUG(85): 5bff988c a7d3d31b /system/ lib/libutils.so 07-21 16:59:26.930: INFO/DEBUG(85): 5bff9890 5bff98a0 07-21 16:59:26.930: INFO/DEBUG(85): 5bff9894 a7d4140f /system/ lib/libutils.so 07-21 16:59:26.930: INFO/DEBUG(85): 5bff9898 07-21 16:59:26.930: INFO/DEBUG(85): 5bff989c 0002 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98a0 003b80b0 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98a4 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98a8 003b80b8 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98ac 80d0 /system/ bin/app_process 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98b0 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98b4 0014 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98b8 80d0 /system/ bin/app_process 07-21 16:59:26.930: INFO/DEBUG(85): 5bff98bc 0001 07-21
