I have an Activity that is running out of memory in CreateSurface. The
logcat looks like this:
10-04 18:33:06.185: ERROR/SurfaceFlinger(1086): createSurface()
failed, generateId = -12
10-04 18:33:06.185: WARN/WindowManager(1086): OutOfResourcesException
creating surface
10-04 18:33:06.185: INFO/WindowManager(1086): Out of memory for
surface! Looking for leaks...
10-04 18:33:06.185: WARN/WindowManager(1086): No leaked surfaces;
killing applicatons!
10-04 18:33:06.185: WARN/ActivityManager(1086): Killing processes Free
memory at adjustment 0
10-04 18:33:06.185: WARN/ActivityManager(1086): Killing
ProcessRecord{449ccbf8 12903:com.quickdroid/10064} (adj 0): Free
memory
10-04 18:33:06.185: WARN/WindowManager(1086): Looks like we have
reclaimed some memory, clearing surface for retry.
10-04 18:33:06.185: WARN/WindowManager(1086): Due to memory failure,
waiting a bit for next layout
10-04 18:33:06.443: INFO/WindowManager(1086): WIN DEATH:
Window{44a5fa98 Internal Logic Error paused=false}
10-04 18:33:06.706: INFO/WindowManager(1086): WIN DEATH:
Window{44a45658 Internal Logic Error paused=false}
10-04 18:33:06.708: INFO/WindowManager(1086): WIN DEATH:
Window{44933ac0 Internal Logic Error paused=false}
10-04 18:33:06.708: INFO/WindowManager(1086): WIN DEATH:
Window{4492c128 Internal Logic Error paused=false}
The Allocation Tracker doesn't show any unusual memory usage right up
to the end of my onCreate method where I placed a breakpoint. Allowing
the framework to proceed with drawing generates an exception as seen
above and the application is killed.
The phrase "Internal Logic Error" makes me wonder if I've hit a bug.
--
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
