search

namgk / ambienttalk

Automatically exported from code.google.com/p/ambienttalk
0 stars 0 forks source link

Android: AmbientTalk causes Dalvik to crash if wireless is not enabled #57

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
AmbientTalk Android applications reproducibly crash if wireless is not enabled 
when they are started.
Elisa grabbed stack traces from a couple of devices, these are attached.
From what I can tell, these errors stem from resource exhaustion.

Sample error:
03-13 21:44:10.101: I/dalvikvm(906): Jit: resizing JitTable from 4096 to 8192
03-13 21:44:10.242: E/dalvikvm-gc(906): Could not mmap 4079616-byte ashmem 
region 'dalvik-mark-stack'
03-13 21:44:10.242: E/dalvikvm-heap(906): dvmHeapBeginMarkStep failed; aborting

More investigation is needed, but for now we can force wireless to ON before we 
start.
It's possible that enabling the wireless interface is enough, it doesn't have 
to be connected to a network.
This also needs to be tested.

Affected devices:
Galaxy Nexus (4.0.x): WORKS
Xperia Mini (2.1): WORKS, but logcat spams "unclassified errno 19 (No such 
device)"
Motorola Xoom (3.2): CRASHES after a while with java.lang.NoClassDefFoundError 
[generic] or OutOfResourcesException locking surface
Nexus S (2.3.6): CRASHES at startup, with "Could not mmap 4079616-byte ashmem 
region 'dalvik-mark-stack'"
HTC Sensation (2.3.4): CRASHES at startup, with "Could not mmap 3416064-byte 
ashmem region 'dalvik-mark-stack'"

Original issue reported on code.google.com by Botje.linux@gmail.com on 15 Mar 2012 at 4:00

Attachments:

GoogleCodeExporter commented 8 years ago 
Tested on my upgraded phone:
HTC Sensation (4.0.3): WORKS

Can we assume this issue was fixed somewhere in the 4.0.x line?
We should force the network on for our apps anyway, just to be sure.

Original comment by Botje.linux@gmail.com on 10 Apr 2012 at 2:43