Fixed
Status Update
Comments
ww...@gmail.com <ww...@gmail.com> #2
a concerning line is:
emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3
what is the CPU in your computer?
The new emulator system requirements are posted here:
http://tools.android.com/tech-docs/emulator
emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3
what is the CPU in your computer?
The new emulator system requirements are posted here:
am...@google.com <am...@google.com>
am...@google.com <am...@google.com> #3
The processor is an AMD Phenom II x6 1075T, and it has AMD-V, as required by the new Android emulator in Linux (please see this link for more info on this CPU : http://www.cpu-world.com/CPUs/K10/AMD-Phenom%20II%20X6%201075T%20-%20HDT75TFBK6DGR.html )
It does not have SSSE3, but I don't see it as a requirement in the Android emulator specs.
It does not have SSSE3, but I don't see it as a requirement in the Android emulator specs.
Description
"Binder:1428_9" prio=-10 tid=182 Runnable
| obj=0x453a self=0x72ca2300c0
| sysTid=2925 nice=-10
| locks_capacity=8
kernel: (couldn't read /proc/self/task/2925/stack)
native: #00 pc 000000000002dafc /apex/com.android.runtime/lib64/bionic/libc.so (syscall+28)
native: #01 pc 0000000000031844 /apex/com.android.runtime/lib64/bionic/libc.so (__futex_wait_ex(void volatile*, bool, int, bool, timespec const*)+140)
native: #02 pc 0000000000090f28 /apex/com.android.runtime/lib64/bionic/libc.so (NonPI::MutexLockWithTimeout(pthread_mutex_internal_t*, bool, timespec const*)+212)
native: #03 pc 000000000005fbf0 /system/lib64/libc++.so (std::__1::mutex::lock()+8)
native: #04 pc 0000000000003010 /system/lib64/libappfuse.so (android::fuse::FuseBridgeLoop::AddBridge(int, android::base::unique_fd_impl<android::base::DefaultCloser>, android::base::unique_fd_impl<android::base::DefaultCloser>)+108)
native: #05 pc 00000000000391a4 /system/lib64/libandroid_servers.so (android::(anonymous namespace)::com_android_server_storage_AppFuseBridge_add_bridge(_JNIEnv*, _jobject*, long, int, int)+284)
native: #06 pc 0000000000cadf50 /system/lib64/libmaplecore-all.so (MCC_CallSlowNative5+96)
at com.android.server.storage.AppFuseBridge.native_add_bridge(Native Method)
at com.android.server.storage.AppFuseBridge.addBridge(AppFuseBridge.java:66)
- locked <0x22f35508> (a Lcom/android/server/storage/AppFuseBridge;) (lock_word:0x40002a00)
at com.android.server.StorageManagerService.mountProxyFileDescriptorBridge(StorageManagerService.java:3423)
- locked <0x1e38ff48> (a Ljava/lang/Object;) (lock_word:0x000000b6)
at android.os.storage.IStorageManager$Stub.onTransact(IStorageManager.java:1289)
at android.os.Binder.execTransactInternal(Binder.java:1028)
at android.os.Binder.execTransact(Binder.java:998)
"AppFuseBridge" prio=0 tid=208 Blocked
| obj=0xcb86 self=0x72461dfec0
| sysTid=8958 nice=0
| locks_capacity=8
kernel: (couldn't read /proc/self/task/8958/stack)
native: #00 pc 000000000002dafc /apex/com.android.runtime/lib64/bionic/libc.so (syscall+28)
native: #01 pc 0000000000008974 /system/lib64/libcommon_bridge.so (maple::ConditionVariable::WaitHoldingLocks(maple::IThread*)+148)
native: #02 pc 000000000000116c /system/lib64/libcommon_bridge.so (maple::Monitor::Lock(maple::IThread*)+1180)
native: #03 pc 000000000000250c /system/lib64/libcommon_bridge.so (maple::Monitor::MonitorEnter(maple::IThread*, _jobject*)+740)
native: #04 pc 0000000000c47cdc /system/lib64/libmaplecore-all.so (MRT_BuiltinSyncEnter+152)
at com.android.server.storage.AppFuseBridge.onClosed(AppFuseBridge.java:119)
- waiting to lock <0x22f35508> (a Lcom/android/server/storage/AppFuseBridge;) (lock_word:0x40002a00) held by thread 182
at com.android.server.storage.AppFuseBridge.native_start_loop(Native Method)
at com.android.server.storage.AppFuseBridge.run(AppFuseBridge.java:82)
at java.lang.Thread.run(Thread.java:929)
```
The above trace states the dead lock quite clearly, I don't think attaching another bugreport is necessary then.