I'm testing my application on WVGA854 emulator. I use two activities
with GL surface one is a menu and second is game itself. While
launching game in logcat there is a message about out of memory error
and application is killed:
10-24 12:42:49.860: DEBUG/Blockx.GameController(900): Surface created
10-24 12:42:49.890: ERROR/SurfaceFlinger(577): not enough memory for
layer bitmap size=1642496 (w=480, h=854, stride=480, format=1)
10-24 12:42:49.890: DEBUG/MemoryDealer(577): LayerBitmap (0x2e9350,
size=8388608)
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 0: 002e9388 |
0x00000000 | 0x0003E000 | F
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 1: 00373ab0 |
0x0003E000 | 0x00191000 | A
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 2: 00373b78 |
0x001CF000 | 0x00191000 | A
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 3: 0028bd40 |
0x00360000 | 0x0003E000 | F
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 4: 002ce748 |
0x0039E000 | 0x00059000 | A
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 5: 002ce7c0 |
0x003F7000 | 0x00059000 | A
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 6: 00374bb0 |
0x00450000 | 0x00191000 | A
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 7: 00375ec8 |
0x005E1000 | 0x00059000 | A
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 8: 00377c30 |
0x0063A000 | 0x00059000 | A
10-24 12:42:49.890: DEBUG/MemoryDealer(577): 9: 00377d50 |
0x00693000 | 0x0016D000 | F
10-24 12:42:49.890: DEBUG/MemoryDealer(577): size allocated: 6385664
(6236 KB)
10-24 12:42:49.900: ERROR/SurfaceFlinger(577): resizing buffer 1 to
(480,854) failed [fffffff4] Unknown error: -12
10-24 12:42:49.930: ERROR/SurfaceComposerClient(577): surface (id=0,
identity=12) is invalid, err=-12 (Out of memory)
10-24 12:42:49.940: WARN/WindowManager(577): Failure showing surface
Surface(native-token=3635864) in Window{43886518
com.beepstreet.blockx_trial/com.beepstreet.blockx_trial.GameActivity
paused=false}
10-24 12:42:49.940: INFO/WindowManager(577): Out of memory for
surface! Looking for leaks...
10-24 12:42:49.960: WARN/WindowManager(577): No leaked surfaces;
killing applicatons!
10-24 12:42:49.960: WARN/ActivityManager(577): Killing processes for
memory at adjustment 0
10-24 12:42:49.960: WARN/ActivityManager(577): Killing for memory:
ProcessRecord{438d9618 900:com.beepstreet.blockx_trial/10023} (adj 0)
10-24 12:42:49.980: INFO/Process(577): Sending signal. PID: 900 SIG: 9
10-24 12:42:50.020: WARN/WindowManager(577): Looks like we have
reclaimed some memory, clearing surface for retry.
10-24 12:42:50.020: WARN/SurfaceComposerClient(577): Destroying
surface while a transaction is open. Client 0x2cc7a8: destroying
surface 0, mTransactionOpen=1
As I understand MemoryDealer debug dumps surface allocator structure
and indeed largest free block is smaller than requested 1642496 bytes.
My question is if same limit will be on real devices?
--
Bart (arcone1) Janusz
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
