Hi,
I also met the binder kmemleaks.
The followings are the logs:
Do you have any idea about the issue further?
unreferenced object 0xe4e93aa0 (size 64):
comm "system_server", pid 400, jiffies 4294940119 (age 68793.640s)
hex dump (first 32 bytes):
72 0c 00 00 a4 3a e9 e4 a4 3a e9 e4 01 00 00 00 r....:...:......
00 00 00 00 00 00 00 00 00 d0 73 d5 00 92 68 d3 ..........s...h.
backtrace:
[<c010fcc8>] kmem_cache_alloc_trace+0x114/0x1f4
[<c046dfb4>] binder_transaction+0x2a0/0x108c
[<c046efec>] binder_thread_write+0x24c/0xf58
[<c0470bf8>] binder_ioctl+0x258/0x614
[<c0124d48>] do_vfs_ioctl+0x7c/0x290
[<c0124f94>] sys_ioctl+0x38/0x5c
[<c000ea80>] ret_fast_syscall+0x0/0x30
[<ffffffff>] 0xffffffff
unreferenced object 0xe4d4e860 (size 64):
comm "er.ServerThread", pid 414, jiffies 4294949454 (age 68700.310s)
hex dump (first 32 bytes):
82 4a 00 00 64 e8 d4 e4 64 e8 d4 e4 01 00 00 00 .J..d...d.......
00 00 00 00 00 00 00 00 00 8c 86 c4 00 00 00 00 ................
backtrace:
[<c010fcc8>] kmem_cache_alloc_trace+0x114/0x1f4
[<c046dfb4>] binder_transaction+0x2a0/0x108c
[<c046efec>] binder_thread_write+0x24c/0xf58
[<c0470bf8>] binder_ioctl+0x258/0x614
[<c0124d48>] do_vfs_ioctl+0x7c/0x290
[<c0124f94>] sys_ioctl+0x38/0x5c
[<c000ea80>] ret_fast_syscall+0x0/0x30
[<ffffffff>] 0xffffffff
unreferenced object 0xd94a8ce0 (size 64):
comm "WindowManager", pid 464, jiffies 4294949455 (age 68700.300s)
hex dump (first 32 bytes):
85 4a 00 00 e4 8c 4a d9 e4 8c 4a d9 01 00 00 00 .J....J...J.....
00 00 00 00 00 00 00 00 00 8c 86 c4 00 00 00 00 ................
backtrace:
[<c010fcc8>] kmem_cache_alloc_trace+0x114/0x1f4
[<c046dfb4>] binder_transaction+0x2a0/0x108c
[<c046efec>] binder_thread_write+0x24c/0xf58
[<c0470bf8>] binder_ioctl+0x258/0x614
[<c0124d48>] do_vfs_ioctl+0x7c/0x290
[<c0124f94>] sys_ioctl+0x38/0x5c
[<c000ea80>] ret_fast_syscall+0x0/0x30
[<ffffffff>] 0xffffffff
calvin於 2012年6月13日星期三UTC+8下午11時56分26秒寫道：
>
> Hi,
>
> I got a dump from kmemleak as below. Can someone advice how to investigate
> where the possible leakage is?
> I believe it is not a leakage of binder driver itself, but don't have any
> idea where to look into. Thanks.
>
> root@android:/ # cat /d/kmemleak
> unreferenced object 0xd7887980 (size 64):
> comm "Binder Thread #", pid 239, jiffies 4294940178 (age 5561.882s)
> hex dump (first 32 bytes):
> d5 05 00 00 84 79 88 d7 84 79 88 d7 01 00 00 00 .....y...y......
> 00 00 00 00 00 00 00 00 00 b2 88 d7 00 b4 88 d7 ................
> backtrace:
> [<c00e58f8>] create_object+0xf4/0x1e8
> [<c00e15e8>] kmem_cache_alloc+0x13c/0x14c
> [<c02619ac>] binder_transaction+0x300/0xe10
> [<c0262b14>] binder_thread_write+0x658/0xc7c
> [<c0263ee4>] binder_ioctl+0x1e0/0x598
> [<c00f6c88>] vfs_ioctl+0x24/0x40
> [<c00f7844>] do_vfs_ioctl+0x1a4/0x1b4
> [<c00f7888>] sys_ioctl+0x34/0x54
> [<c0048740>] ret_fast_syscall+0x0/0x3c
> [<ffffffff>] 0xffffffff
> unreferenced object 0xcfd7d100 (size 64):
> comm "Binder Thread #", pid 514, jiffies 4294944066 (age 5531.539s)
> hex dump (first 32 bytes):
> 7f 0f 00 00 04 d1 d7 cf 04 d1 d7 cf 01 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 64 dd d7 00 66 dd d7 .........d...f..
> backtrace:
> [<c00e58f8>] create_object+0xf4/0x1e8
> [<c00e15e8>] kmem_cache_alloc+0x13c/0x14c
> [<c02619ac>] binder_transaction+0x300/0xe10
> [<c0262b14>] binder_thread_write+0x658/0xc7c
> [<c0263ee4>] binder_ioctl+0x1e0/0x598
> [<c00f6c88>] vfs_ioctl+0x24/0x40
> [<c00f7844>] do_vfs_ioctl+0x1a4/0x1b4
> [<c00f7888>] sys_ioctl+0x34/0x54
> [<c0048740>] ret_fast_syscall+0x0/0x3c
> [<ffffffff>] 0xffffffff
>
>
--
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
