Clock app crashes at acquiring location

What steps will reproduce the problem?
Open the default clock app from clock widget or app drawer

What is the expected output? What do you see instead?
Clock app doesn't close directly after acquiring location

What version of the product are you using? On what operating system?
2.0.0

Please provide any additional information below.
W/WindowManager( 1017): Force-removing child win Window{4145a458 SurfaceView 
paused=false} from container Window{4144e200 
com.htc.android.worldclock/com.htc.android.worldclock.WorldClockTabControl 
paused=false}
I/ActivityManager( 1017): Process com.htc.android.worldclock (pid 29839) has 
died.
W/ActivityManager( 1017): Force removing ActivityRecord{40fcedd8 
com.htc.android.worldclock/.WorldClockTabControl}: app died, no saved state
D/InputManager( 1017): setFocusedApplication Exception: 
java.lang.NullPointerException
D/WirelessDisplayService( 1017): getMirrorDisplayStatus:falsecurState:1
W/ActivityManager( 1017): handleTopAppChanged(): The previous AP is died 
unexpectedly.
W/WindowManager( 1017): Failed looking up window
W/WindowManager( 1017): java.lang.IllegalArgumentException: Requested window 
android.os.BinderProxy@41454d98 does not exist
W/WindowManager( 1017):         at 
com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerSe
rvice.java)
W/WindowManager( 1017):         at 
com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerSe
rvice.java)
W/WindowManager( 1017):         at 
com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java)
W/WindowManager( 1017):         at 
android.os.BinderProxy.sendDeathNotice(Binder.java)
W/WindowManager( 1017):         at dalvik.system.NativeStart.run(Native Method)
I/WindowState( 1017): WIN DEATH: null

Original issue reported on code.google.com by adrian.s...@gmail.com on 8 Feb 2013 at 10:57

google-code-export / team-venom-viperones

Clock app crashes at acquiring location #64