I'm also able to consistently crash the emulator by sending mock GPS coordinates to it. It immediately prints some memory addresses to the log (which looks a bit like a BSOD), then after 20 seconds shuts down all the services and reboots, getting stuck on the boot screen. Increasing the memory to 512Mb made no difference.
On Dec 7, 2:13 pm, Raymond Rodgers <[email protected]> wrote: > I've noticed that the 2.3 emulator seems to be a lot slower overall, and > has a tendency to spontaneously reboot. Has anyone else noticed this? I > have updated two machines to use the latest SDK and ADT, one is on > Fedora 13, the other on 14. I've been using both machines in > development, and they both ran the 2.2 emulator just fine, though I > haven't tried the 2.2 emulator with the latest SDK. > > At first I thought it was my app which might have been triggering the > sluggish performance and reboots, but as I just finished installing the > updates on the F13 machine, and simply ran the 2.3 emulator without > installing my app at all in it when it rebooted while I was trying to > open the Maps application. A key feature of the reboot attempt, by the > way, seems to be that it never completes: I have to close the emulator > altogether, then restart it because it never gets out of the boot > animation. It also isn't sending messages to LogCat. > > This will make working with 2.3 a little bit tougher until it gets > pushed to my Nexus One... :-) > Raymond > > -- > Raymond Rodgershttp://www.badlucksoft.com/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
