Deezer Android SDK频繁崩溃
下面是一个典型的碰撞:Deezer Android SDK频繁崩溃,android,deezer,Android,Deezer,下面是一个典型的碰撞: 13:37:36.166 23654-23669/com.soundrop.android V/dalvikvm﹕ +++ calling dlsym(Java_com_deezer_sdk_player_impl_RealPlayerImpl_cStop) 13:37:36.166 23654-23669/com.soundrop.android V/dalvikvm﹕ Found 'Java_com_deezer_sdk_player_impl_RealPlaye
13:37:36.166 23654-23669/com.soundrop.android V/dalvikvm﹕ +++ calling dlsym(Java_com_deezer_sdk_player_impl_RealPlayerImpl_cStop)
13:37:36.166 23654-23669/com.soundrop.android V/dalvikvm﹕ Found 'Java_com_deezer_sdk_player_impl_RealPlayerImpl_cStop' with dlsym
13:37:36.178 23654-23901/com.soundrop.android A/libc﹕ Fatal signal 11 (SIGSEGV) at 0x6174658f (code=1), thread 23901 (Thread-369)
13:37:36.278 103-103/? I/DEBUG﹕ *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
13:37:36.278 103-103/? I/DEBUG﹕ Build fingerprint: 'generic/vbox86p/vbox86p:4.2.2/JDQ39E/eng.buildbot.20130923.154959:userdebug/test-keys'
13:37:36.278 103-103/? I/DEBUG﹕ Revision: '0'
13:37:36.278 103-103/? I/DEBUG﹕ pid: 23654, tid: 23901, name: Thread-369 >>> com.soundrop.android <<<
13:37:36.278 103-103/? I/DEBUG﹕ signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 6174658f
13:37:36.454 103-103/? I/DEBUG﹕ eax b7536e10 ebx b759dff4 ecx 61746567 edx 00000003
13:37:36.454 103-103/? I/DEBUG﹕ esi 61746567 edi 22030020
13:37:36.454 103-103/? I/DEBUG﹕ xcs 00000073 xds 0000007b xes 0000007b xfs 00000043 xss 0000007b
13:37:36.454 103-103/? I/DEBUG﹕ eip b7536e2f ebp 967188f4 esp 967188ac flags 00010292
13:37:36.454 103-103/? I/DEBUG﹕ backtrace:
13:37:36.454 103-103/? I/DEBUG﹕ #00 pc 00031e2f /system/lib/libc.so (ftell+31)
13:37:36.454 103-103/? I/DEBUG﹕ #01 pc 0012fc73 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #02 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #03 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #04 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #05 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #06 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #07 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #08 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #09 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #10 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #11 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #12 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #13 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #14 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #15 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #16 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #17 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #18 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #19 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #20 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #21 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #22 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #23 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #24 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #25 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #26 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #27 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #28 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #29 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #30 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ #31 pc 0002e020 <unknown>
13:37:36.454 103-103/? I/DEBUG﹕ stack:
13:37:36.454 103-103/? I/DEBUG﹕ 9671886c 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718870 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718874 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718878 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 9671887c 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718880 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718884 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718888 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 9671888c 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718890 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718894 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 96718898 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 9671889c 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188a0 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188a4 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188a8 00000000
13:37:36.454 103-103/? I/DEBUG﹕ #00 967188ac 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188b0 96b50ba0 /system/lib/libhoudini.so
13:37:36.454 103-103/? I/DEBUG﹕ 967188b4 380078d7 /data/app-lib/com.soundrop.android-2/libdeezer.so
13:37:36.454 103-103/? I/DEBUG﹕ 967188b8 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188bc 967188dc [stack:23901]
13:37:36.454 103-103/? I/DEBUG﹕ 967188c0 96b50d4d /system/lib/libhoudini.so
13:37:36.454 103-103/? I/DEBUG﹕ 967188c4 200d64f0
13:37:36.454 103-103/? I/DEBUG﹕ 967188c8 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188cc 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188d0 61746567
13:37:36.454 103-103/? I/DEBUG﹕ 967188d4 22030020
13:37:36.454 103-103/? I/DEBUG﹕ 967188d8 96bc3f5b /system/lib/libhoudini.so
13:37:36.454 103-103/? I/DEBUG﹕ 967188dc 61746567
13:37:36.454 103-103/? I/DEBUG﹕ 967188e0 96b4f04f /system/lib/libhoudini.so
13:37:36.454 103-103/? I/DEBUG﹕ 967188e4 00000000
13:37:36.454 103-103/? I/DEBUG﹕ 967188e8 00000000
13:37:36.454 103-103/? I/DEBUG﹕ ........ ........
13:37:36.458 103-103/? I/DEBUG﹕ #01 967188fc 000007c5
13:37:36.458 103-103/? I/DEBUG﹕ ........ ........
13:37:36.458 103-103/? I/DEBUG﹕ #02 22030008 220301c0
13:37:36.458 103-103/? I/DEBUG﹕ ........ ........
13:37:36.458 103-103/? I/DEBUG﹕ memory map around fault addr 6174658f:
13:37:36.458 103-103/? I/DEBUG﹕ 3861f000-40000000
13:37:36.458 103-103/? I/DEBUG﹕ (no map for address)
13:37:36.458 103-103/? I/DEBUG﹕ 95e25000-95e26000
13:37:36.166 23654-23669/com.soundrop.android V/dalvikvm﹕ +++ 调用dlsym(Java_com_deezer_sdk_player_impl_RealPlayerImpl_cStop)
13:37:36.166 23654-23669/com.soundrop.android V/dalvikvm﹕ 找到带有dlsym的“Java_com_deezer_sdk_player_impl_RealPlayerImpl_cStop”
13:37:36.178 23654-23901/com.soundrop.android A/libc﹕ 0x6174658f(代码=1)、螺纹23901(螺纹-369)处的致命信号11(SIGSEGV)
13:37:36.278 103-103/? I/DEBUG﹕ *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
13:37:36.278 103-103/? I/DEBUG﹕ 构建指纹:“generic/vbox86p/vbox86p:4.2.2/JDQ39E/eng.buildbot.20130923.154959:用户调试/测试密钥”
13:37:36.278 103-103/? I/DEBUG﹕ 修订:“0”
13:37:36.278 103-103/? I/DEBUG﹕ pid:23654,tid:23901,name:Thread-369>>>com.soundrop.android我注意到在堆栈跟踪中有一些对/system/lib/libhoudini.so的调用,这让我认为这是在android仿真器中发生的。我说得对吗?您在真实设备上也有这个问题吗?这是正确的(我在开发时使用)。目前还不知道它是否发生在真正的设备上,但会在进一步测试后让您知道。这似乎发生在两个曲目之间,我怀疑这是一个比赛条件,其中一个曲目正在结束,应用程序同时调用stop()。我将等待您在真实设备上的反馈,因为堆栈跟踪本身(#…pc 00005520)从来没有直接暗示libdeeezer.so,并且仅是/system/lib/libc.so/system/lib/libhoudini.so。我的猜测是模拟器在libc.so(标准c库)中添加了一些操作,这导致了这种崩溃。我可以在堆栈跟踪中看到libdeezer,但我想很难确定到底发生了什么。我已经在手机上测试了一段时间,但还不能重现这个问题。我会随时通知你。你在模拟器上设置了多少RAM/堆大小?发生这些故障的原因可能是内存不足(我刚刚遇到了一个只有96MB内存的自动AVD的同样问题)