It looks like a bug in the system, I'd suggest filing a bug report. :)
On Apr 21, 1:14 pm, Michael Rueger <[EMAIL PROTECTED]> wrote:
> Bump (now that it is not the last minute submit panic anymore)
>
> anyone else seen this?
>
> Michael
>
> Danilo Gulamhussene wrote:
> > Hi all,
>
> > I have a problem with updating proximity Alerts.
> > Some times the emulator crashes when I try to update the registration for
> > an proximity alert.
> > The relevant code for updating is as follows:
>
> > mLocationManager.removeProximityAlert(i);
>
> > mLocationManager.addProximityAlert(
> > (double)place.getLatitude() / 1E6,
> > (double)place.getLongitude() / 1E6,
> >
> > (float)((PlaceLocationDetector)place.getDetector()).getRange(),
> > 10000000, //FIXME change
> > expiration to -1 when sdk is fixed
> > i);
> > mRegisteredProximityAlerts.put(place.getRowID(), i);
>
> > The resulting stack dump:
>
> > DEBUG/LocationManager(715): addProximityAlert: latitude = 37.461734,
> > longitude = -122.144394, radius = 305.0, expiration = 10000000, intent =
> > Intent { action=android.intent.action.PROXIMITY_ALERT
> > extras=Bundle[{_id=1}] }
> > DEBUG/LocationManagerService(508): addProximityAlert: latitude = 37.461734,
> > longitude = -122.144394, expiration = 10000000, intent = Intent {
> > action=android.intent.action.PROXIMITY_ALERT extras=Bundle[{_id=1}] }
> > DEBUG/LocationManagerService(508): loadProviders
> > DEBUG/LocationManagerService(508): loadProviders: already loaded
> > DEBUG/LocationManager(715): addProximityAlert: latitude = 37.457836,
> > longitude = -122.133036, radius = 305.0, expiration = 10000000, intent =
> > Intent { action=android.intent.action.PROXIMITY_ALERT
> > extras=Bundle[{_id=2}] }
> > DEBUG/LocationManagerService(508): addProximityAlert: latitude = 37.457836,
> > longitude = -122.133036, expiration = 10000000, intent = Intent {
> > action=android.intent.action.PROXIMITY_ALERT extras=Bundle[{_id=2}] }
> > DEBUG/LocationManagerService(508): loadProviders
> > DEBUG/LocationManagerService(508): loadProviders: already loaded
> > DEBUG/dalvikvm(508): Exception Ljava/util/ConcurrentModificationException;
> > from HashMap.java:108 not caught locally
> > WARN/dalvikvm(508): threadid=15: thread exiting with uncaught exception
> > (group=0x4000fdf8)
> > ERROR/AndroidRuntime(508): Uncaught handler: thread
> > android.server.ServerThread exiting due to uncaught exception
> > ERROR/AndroidRuntime(508): *** EXCEPTION IN SYSTEM PROCESS. System will
> > crash.
> > ERROR/AndroidRuntime(508): java.util.ConcurrentModificationException
> > ERROR/AndroidRuntime(508): at
> > java.util.HashMap$HashMapIterator.checkConcurrentMod(HashMap.java:108)
> > ERROR/AndroidRuntime(508): at
> > java.util.HashMap$HashMapIterator.next(HashMap.java:113)
> > ERROR/AndroidRuntime(508): at
> > android.server.LocationManagerService.handleLocationChanged(LocationManagerService.java:821)
> > ERROR/AndroidRuntime(508): at
> > android.server.LocationManagerService$LocationWorkerHandler.handleMessage(LocationManagerService.java:860)
> > ERROR/AndroidRuntime(508): at
> > android.os.Handler.dispatchMessage(Handler.java:80)
> > ERROR/AndroidRuntime(508): at android.os.Looper.loop(Looper.java:91)
> > ERROR/AndroidRuntime(508): at
> > android.server.ServerThread.run(SystemServer.java:259)
>
> > Any ideas on what might go wrong here?
> > Is it a known problem or are we doing something wrong here?
>
> > thanks,
>
> > Danilo Gulamhussene
--~--~---------~--~----~------------~-------~--~----~
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
[EMAIL PROTECTED]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
