AdMob的反复启动应用程序时崩溃模拟器 [英] AdMob crashes emulator when launching app repeatedly

查看:246
本文介绍了AdMob的反复启动应用程序时崩溃模拟器的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图调试应用程序,有广告在里面,和仿真器崩溃在我身上。看来愚蠢的,我必须手动将它设置为测试模式,当我试图测试出我的code。有好歹prevent这种情况的发生,perhapse检测,如果它在仿真器模式,并将它设置adRequest测试模式?有没有其他人能够克服这种或有经验吗?至少我不能重新在我的手机的问题。

下面是我认为的code部分导致了我的问题,当我使用Android模拟器:

  AD浏览报AD浏览报=新的AD浏览报(这一点,AdSize.BANNER,XXXXXX);
的LinearLayout布局=(的LinearLayout)this.findViewById(R.id.adview_layout);
layout.addView(AD浏览报);
AdRequest adRequest =新AdRequest();
adView.loadAd(adRequest);
 

下面是日志从LogCat中:

 十月7号至5号:45:10.627:信息/ ActivityManager(70):启动活动:意向{DAT =内容://com.simpleclock.widget/appwidgets/1 CMP = hobodroid.clock.widget / .Settings(有群众演员)}
十月七日至5日:45:10.627:WARN / ActivityManager(70):startActivity非活动范围内调用;迫使Intent.FLAG_ACTIVITY_NEW_TASK为:意向{DAT =内容://com.simpleclock.widget/appwidgets/1 CMP = hobodroid.clock.widget / .Settings(有群众演员)}
十月七日至5日:45:10.977:信息/广告(3527):为了得到这个设备上测试广告,呼吁adRequest.addTestDevice(AdRequest.TEST_EMULATOR);
十月七日至5日:45:11.037:信息/广告(3527):adRequestUrlHtml:LT; HTML&GT;&LT; HEAD&GT;&LT;脚本src="http://www.gstatic.com/afma/sdk-core-v40.js"></script><script>AFMA_buildAdURL({"msid":"hobodroid.clock.widget","simulator":1,"hl":"en","$p$pqs":1,"u_so":"p","slotname":"a14e0eda6eb26ea","js":"afma-sdk-a-v4.1.0","app_name":"8.android.hobodroid.clock.widget","isu":"B3EEABB8EE11C2BE770B684D95219ECB","u_audio":4,"u_w":320,"cap":"m,a","format":"320x50_mb","u_sd":1.5,"net":"ed","u_h":533});</script></head><body></body></html>
十月七日至5日:45:11.307:信息/ ActivityManager(70):显示活动hobodroid.clock.widget / .Settings:662毫秒(总662毫秒)
十月七日至5日:45:11.947:信息/广告(3527):接收到的广告网址:&LT;网址: "http://r.admob.com:80/ad_source.php?msid=hobodroid.clock.widget&hl=en&$p$pqs=1&u_so=p&slotname=a14e0eda6eb26ea&js=afma-sdk-a-v4.1.0&app_name=8.android.hobodroid.clock.widget&isu=B3EEABB8EE11C2BE770B684D95219ECB&u_audio=4&u_w=320&cap=m%2Ca&format=320x50_mb&u_sd=1.5&net=ed&u_h=533&output=html&region=mobile_app&u_tz=-120&ex=1&client_sdk=1&askip=1", afmaNotifyDt:空&GT;
十月七日至5日:45:12.427:信息/广告(3527):onReceiveAd()
十月七日至5日:45:13.217:WARN / KeyCharacterMap(3527):没有键盘ID 0
十月七日至5日:45:13.217:WARN / KeyCharacterMap(3527):使用默认的键盘对应:/system/usr/keychars/qwerty.kcm.bin
十月七日至5日:45:14.307:信息/ DEBUG(27):*** *** *** *** *** *** *** *** *** *** *** * ** *** *** *** ***
十月七日至5日:45:14.317:信息/ DEBUG(27):构建指纹:通用/ SDK /通用/:1.6 /甜甜圈/ 20842:ENG /测试键
十月七日至5日:45:14.317:信息/ DEBUG(27):PID:3527,TID:3537&GT;&GT;&GT; hobodroid.clock.widget&LT;&LT;&LT;
十月七日至5日:45:14.317:信息/ DEBUG(27):11(SIGSEGV),故障地址00000000
十月七日至5日:45:14.317:信息/ DEBUG(27):R0,R1 00000007 R2 411b9a50 R3 411b9a50 00000000
十月七日至5日:45:14.317:信息/ DEBUG(27):R4 411b9a50 R5 00280df0 R6 00000000 R7 44cc8cac
十月七日至5日:45:14.317:信息/ DEBUG(27):R8 44cc8da0 R9 424c2e48 10 424c2e34 FP 00000001
十月七日至5日:45:14.317:信息/ DEBUG(27):IP ad083e5c SP 44cc8c48 LR ad047361 PC ad03fc86 CPSR 00000030
十月七日至5日:45:14.487:信息/ DEBUG(27):#00件0003fc86 /system/lib/libdvm.so
十月七日至5日:45:14.498:信息/ DEBUG(27):#01件0002f480 /system/lib/libdvm.so
十月七日至5日:45:14.498:信息/ DEBUG(27):#02件001f3c52 /system/lib/libwebcore.so
十月七日至5日:45:14.498:信息/ DEBUG(27):#03件00260b62 /system/lib/libwebcore.so
十月七日至5日:45:14.498:信息/ DEBUG(27):#04件000dac80 /system/lib/libwebcore.so
十月七日至5日:45:14.498:信息/ DEBUG(27):#05件000ecc6c /system/lib/libwebcore.so
十月七日至5日:45:14.507:信息/ DEBUG(27):#06件000df90c /system/lib/libwebcore.so
十月七日至5日:45:14.507:信息/ DEBUG(27):#07件00188640 /system/lib/libwebcore.so
十月七日至5日:45:14.507:信息/ DEBUG(27):#08件001887bc /system/lib/libwebcore.so
十月七日至5日:45:14.507:信息/ DEBUG(27):#09件001887e8 /system/lib/libwebcore.so
十月七日至5日:45:14.507:信息/ DEBUG(27):#10件00258ab6 /system/lib/libwebcore.so
十月七日至5日:45:14.507:信息/ DEBUG(27):#11件0000e434 /system/lib/libdvm.so
十月七日至5日:45:14.517:信息/ DEBUG(27):#12件00040b0e /system/lib/libdvm.so
十月七日至5日:45:14.517:信息/ DEBUG(27):#13件00013198 /system/lib/libdvm.so
十月七日至5日:45:14.517:信息/ DEBUG(27):#14件00017be4 /system/lib/libdvm.so
十月七日至5日:45:14.517:信息/ DEBUG(27):#15件0001762c /system/lib/libdvm.so
十月七日至5日:45:14.517:信息/ DEBUG(27):#16件0005282c /system/lib/libdvm.so
十月七日至5日:45:14.517:信息/ DEBUG(27):#17件0005284a /system/lib/libdvm.so
十月七日至5日:45:14.517:信息/ DEBUG(27):#18件00047800 /system/lib/libdvm.so
十月七日至5日:45:14.527:信息/ DEBUG(27):#19件0000f940 /system/lib/libc.so
十月七日至5日:45:14.527:信息/ DEBUG(27):#20件0000f4b4 /system/lib/libc.so
十月七日至5日:45:14.527:信息/ DEBUG(27):堆栈:
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c08 44cc8c40
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c0c 00280df0 [堆]
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c10 4182712a /data/dalvik-cache/system@framework@core.jar@classes.dex
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c14 4182712b /data/dalvik-cache/system@framework@core.jar@classes.dex
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c18 00280df0 [堆]
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c1c 00000001
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c20 00000007
十月七日至5日:45:14.527:信息/ DEBUG(27):44cc8c24 4106ffe0的/ dev / ashmem /达尔维克LinearAlloc(删除)
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c28 00280df0 [堆]
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c2c 00000001
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c30 00000007
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c34 ad047361 /system/lib/libdvm.so
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c38 411b9a50的/ dev / ashmem /达尔维克LinearAlloc(删除)
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c3c 00280df0 [堆]
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c40 df002777
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c44 e3a070ad
十月七日至5日:45:14.537:信息/ DEBUG(27):#00 44cc8c48 002cf510 [堆]
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c4c ad06c894 /system/lib/libdvm.so
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c50 ad03ff19 /system/lib/libdvm.so
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c54 ad06c608 /system/lib/libdvm.so
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c58 439ab0d8的/ dev / ashmem / MSPACE / Dalvik的堆/ 2(删除)
十月七日至5日:45:14.537:信息/ DEBUG(27):44cc8c5c ad06c608 /system/lib/libdvm.so
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c60 ad03fc71 /system/lib/libdvm.so
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c64 00297fb8 [堆]
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c68 00000000
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c6c ad02f483 /system/lib/libdvm.so
十月七日至5日:45:14.547:信息/ DEBUG(27):#01 44cc8c70 ad06c608 /system/lib/libdvm.so
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c74 ad02ff11 /system/lib/libdvm.so
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c78 44cc8cac
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c7c 411b9a50的/ dev / ashmem /达尔维克LinearAlloc(删除)
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c80 aa3dc5d0 /system/lib/libwebcore.so
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c84 ad02f409 /system/lib/libdvm.so
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c88 aa1f3c3d /system/lib/libwebcore.so
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c8c 00297fb8 [堆]
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c90 00000000
十月七日至5日:45:14.547:信息/ DEBUG(27):44cc8c94 aa1f3c55 /system/lib/libwebcore.so
十月七日至5日:45:15.077:信息/ ActivityManager(70):启动活动:意向{DAT =内容://com.simpleclock.widget/appwidgets/1 CMP = hobodroid.clock.widget / .Settings(有额外) }
十月七日至5日:45:15.077:WARN / ActivityManager(70):startActivity非活动范围内调用;迫使Intent.FLAG_ACTIVITY_NEW_TASK为:意向{DAT =内容://com.simpleclock.widget/appwidgets/1 CMP = hobodroid.clock.widget / .Settings(有群众演员)}
十月七日至5日:45:15.577:信息/广告(3527):为了得到这个设备上测试广告,呼吁adRequest.addTestDevice(AdRequest.TEST_EMULATOR);
十月七日至5日:45:15.637:信息/广告(3527):adRequestUrlHtml:LT; HTML&GT;&LT; HEAD&GT;&LT;脚本src="http://www.gstatic.com/afma/sdk-core-v40.js"></script><script>AFMA_buildAdURL({"msid":"hobodroid.clock.widget","simulator":1,"hl":"en","$p$pqs":2,"u_so":"p","slotname":"a14e0eda6eb26ea","js":"afma-sdk-a-v4.1.0","app_name":"8.android.hobodroid.clock.widget","isu":"B3EEABB8EE11C2BE770B684D95219ECB","u_audio":4,"u_w":320,"cap":"m,a","format":"320x50_mb","u_sd":1.5,"net":"ed","u_h":533});</script></head><body></body></html>
十月七日至5日:45:15.877:信息/ ActivityManager(70):显示活动hobodroid.clock.widget / .Settings:796毫秒(总796毫秒)
十月七日至5日:45:16.887:信息/ ActivityManager(70):过程hobodroid.clock.widget(PID 3527)已死亡。
十月七日至5日:45:16.887:WARN / ActivityManager(70):坠毁服务hobodroid.clock.widget调度启动/ .ClockService在5000毫秒
十月七日至5日:45:16.897:信息/窗口管理器(70):WIN死亡:窗口{43856840 hobodroid.clock.widget / hobodroid.clock.widget.Settings暂停= FALSE}
十月七日至5日:45:16.937:WARN / UsageStats(70):com.android.launcher意外的简历时,如果已经恢复了hobodroid.clock.widget
十月七日至5日:45:16.987:ERROR / ActivityThread(70):未能找到android.server.checkin供应商信息
十月七日至5日:45:16.987:警告/签(70):无法登录事件SYSTEM_SERVICE_LOOPING:java.lang.IllegalArgumentException:如果未知的URL内容://android.server.checkin/events
十月七日至5日:45:16.997:WARN / InputManagerService(70):得到的RemoteException发送SETACTIVE(假)通知,为PID 3527 UID 10024
 

解决方案

这个问题是这里<一个讨论href="https://groups.google.com/group/google-admob-ads-sdk/browse_thread/thread/f72ed8694a28cc7d/ced66f77ddb1e3ad" rel="nofollow">https://groups.google.com/group/google-admob-ads-sdk/browse_thread/thread/f72ed8694a28cc7d/ced66f77ddb1e3ad这里的http://groups.google.com/group/google-admob-ads-sdk/browse_thread/thread/eeb307a33a69765d.建议的解决方法是调用adView.destroy()的Activity.onDestroy()。似乎有帮助。

  @覆盖
保护无效的onDestroy(){
    super.onDestroy();

    //办法来解决1.6 AdMob的崩溃
    AD浏览报AD浏览报=(AD浏览报)findViewById(R.id.adView);
    如果(AD浏览报!= NULL)
        adView.destroy();
}
 

I'm trying to debug an app that has ads in it, and the emulator is crashing on me. It seems silly that I have to manually set it to test mode, when I'm trying to test out my code. Is there someway to prevent this from happening, perhapse detect if its in emulator mode and have it set the adRequest to test mode? Has anyone else been able to overcome this or experienced it? I can't recreate the problem on my phone at least.

Here is the code section that I think is causing me problems, when I'm using the Android emulator:

AdView adView = new AdView(this, AdSize.BANNER, "xxxxxx");
LinearLayout layout = (LinearLayout) this.findViewById(R.id.adview_layout);
layout.addView(adView);
AdRequest adRequest = new AdRequest();
adView.loadAd(adRequest);

Here is the log from LogCat:

07-05 10:45:10.627: INFO/ActivityManager(70): Starting activity: Intent { dat=content://com.simpleclock.widget/appwidgets/1 cmp=hobodroid.clock.widget/.Settings (has extras) }
07-05 10:45:10.627: WARN/ActivityManager(70): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { dat=content://com.simpleclock.widget/appwidgets/1 cmp=hobodroid.clock.widget/.Settings (has extras) }
07-05 10:45:10.977: INFO/Ads(3527): To get test ads on this device, call adRequest.addTestDevice(AdRequest.TEST_EMULATOR);
07-05 10:45:11.037: INFO/Ads(3527): adRequestUrlHtml: <html><head><script src="http://www.gstatic.com/afma/sdk-core-v40.js"></script><script>AFMA_buildAdURL({"msid":"hobodroid.clock.widget","simulator":1,"hl":"en","preqs":1,"u_so":"p","slotname":"a14e0eda6eb26ea","js":"afma-sdk-a-v4.1.0","app_name":"8.android.hobodroid.clock.widget","isu":"B3EEABB8EE11C2BE770B684D95219ECB","u_audio":4,"u_w":320,"cap":"m,a","format":"320x50_mb","u_sd":1.5,"net":"ed","u_h":533});</script></head><body></body></html>
07-05 10:45:11.307: INFO/ActivityManager(70): Displayed activity hobodroid.clock.widget/.Settings: 662 ms (total 662 ms)
07-05 10:45:11.947: INFO/Ads(3527): Received ad url: <"url": "http://r.admob.com:80/ad_source.php?msid=hobodroid.clock.widget&hl=en&preqs=1&u_so=p&slotname=a14e0eda6eb26ea&js=afma-sdk-a-v4.1.0&app_name=8.android.hobodroid.clock.widget&isu=B3EEABB8EE11C2BE770B684D95219ECB&u_audio=4&u_w=320&cap=m%2Ca&format=320x50_mb&u_sd=1.5&net=ed&u_h=533&output=html&region=mobile_app&u_tz=-120&ex=1&client_sdk=1&askip=1", "afmaNotifyDt": "null">
07-05 10:45:12.427: INFO/Ads(3527): onReceiveAd()
07-05 10:45:13.217: WARN/KeyCharacterMap(3527): No keyboard for id 0
07-05 10:45:13.217: WARN/KeyCharacterMap(3527): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
07-05 10:45:14.307: INFO/DEBUG(27): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-05 10:45:14.317: INFO/DEBUG(27): Build fingerprint: 'generic/sdk/generic/:1.6/Donut/20842:eng/test-keys'
07-05 10:45:14.317: INFO/DEBUG(27): pid: 3527, tid: 3537  >>> hobodroid.clock.widget <<<
07-05 10:45:14.317: INFO/DEBUG(27): signal 11 (SIGSEGV), fault addr 00000000
07-05 10:45:14.317: INFO/DEBUG(27):  r0 00000007  r1 411b9a50  r2 411b9a50  r3 00000000
07-05 10:45:14.317: INFO/DEBUG(27):  r4 411b9a50  r5 00280df0  r6 00000000  r7 44cc8cac
07-05 10:45:14.317: INFO/DEBUG(27):  r8 44cc8da0  r9 424c2e48  10 424c2e34  fp 00000001
07-05 10:45:14.317: INFO/DEBUG(27):  ip ad083e5c  sp 44cc8c48  lr ad047361  pc ad03fc86  cpsr 00000030
07-05 10:45:14.487: INFO/DEBUG(27):          #00  pc 0003fc86  /system/lib/libdvm.so
07-05 10:45:14.498: INFO/DEBUG(27):          #01  pc 0002f480  /system/lib/libdvm.so
07-05 10:45:14.498: INFO/DEBUG(27):          #02  pc 001f3c52  /system/lib/libwebcore.so
07-05 10:45:14.498: INFO/DEBUG(27):          #03  pc 00260b62  /system/lib/libwebcore.so
07-05 10:45:14.498: INFO/DEBUG(27):          #04  pc 000dac80  /system/lib/libwebcore.so
07-05 10:45:14.498: INFO/DEBUG(27):          #05  pc 000ecc6c  /system/lib/libwebcore.so
07-05 10:45:14.507: INFO/DEBUG(27):          #06  pc 000df90c  /system/lib/libwebcore.so
07-05 10:45:14.507: INFO/DEBUG(27):          #07  pc 00188640  /system/lib/libwebcore.so
07-05 10:45:14.507: INFO/DEBUG(27):          #08  pc 001887bc  /system/lib/libwebcore.so
07-05 10:45:14.507: INFO/DEBUG(27):          #09  pc 001887e8  /system/lib/libwebcore.so
07-05 10:45:14.507: INFO/DEBUG(27):          #10  pc 00258ab6  /system/lib/libwebcore.so
07-05 10:45:14.507: INFO/DEBUG(27):          #11  pc 0000e434  /system/lib/libdvm.so
07-05 10:45:14.517: INFO/DEBUG(27):          #12  pc 00040b0e  /system/lib/libdvm.so
07-05 10:45:14.517: INFO/DEBUG(27):          #13  pc 00013198  /system/lib/libdvm.so
07-05 10:45:14.517: INFO/DEBUG(27):          #14  pc 00017be4  /system/lib/libdvm.so
07-05 10:45:14.517: INFO/DEBUG(27):          #15  pc 0001762c  /system/lib/libdvm.so
07-05 10:45:14.517: INFO/DEBUG(27):          #16  pc 0005282c  /system/lib/libdvm.so
07-05 10:45:14.517: INFO/DEBUG(27):          #17  pc 0005284a  /system/lib/libdvm.so
07-05 10:45:14.517: INFO/DEBUG(27):          #18  pc 00047800  /system/lib/libdvm.so
07-05 10:45:14.527: INFO/DEBUG(27):          #19  pc 0000f940  /system/lib/libc.so
07-05 10:45:14.527: INFO/DEBUG(27):          #20  pc 0000f4b4  /system/lib/libc.so
07-05 10:45:14.527: INFO/DEBUG(27): stack:
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c08  44cc8c40  
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c0c  00280df0  [heap]
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c10  4182712a  /data/dalvik-cache/system@framework@core.jar@classes.dex
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c14  4182712b  /data/dalvik-cache/system@framework@core.jar@classes.dex
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c18  00280df0  [heap]
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c1c  00000001  
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c20  00000007  
07-05 10:45:14.527: INFO/DEBUG(27):     44cc8c24  4106ffe0  /dev/ashmem/dalvik-LinearAlloc (deleted)
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c28  00280df0  [heap]
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c2c  00000001  
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c30  00000007  
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c34  ad047361  /system/lib/libdvm.so
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c38  411b9a50  /dev/ashmem/dalvik-LinearAlloc (deleted)
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c3c  00280df0  [heap]
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c40  df002777  
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c44  e3a070ad  
07-05 10:45:14.537: INFO/DEBUG(27): #00 44cc8c48  002cf510  [heap]
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c4c  ad06c894  /system/lib/libdvm.so
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c50  ad03ff19  /system/lib/libdvm.so
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c54  ad06c608  /system/lib/libdvm.so
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c58  439ab0d8  /dev/ashmem/mspace/dalvik-heap/2 (deleted)
07-05 10:45:14.537: INFO/DEBUG(27):     44cc8c5c  ad06c608  /system/lib/libdvm.so
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c60  ad03fc71  /system/lib/libdvm.so
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c64  00297fb8  [heap]
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c68  00000000  
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c6c  ad02f483  /system/lib/libdvm.so
07-05 10:45:14.547: INFO/DEBUG(27): #01 44cc8c70  ad06c608  /system/lib/libdvm.so
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c74  ad02ff11  /system/lib/libdvm.so
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c78  44cc8cac  
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c7c  411b9a50  /dev/ashmem/dalvik-LinearAlloc (deleted)
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c80  aa3dc5d0  /system/lib/libwebcore.so
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c84  ad02f409  /system/lib/libdvm.so
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c88  aa1f3c3d  /system/lib/libwebcore.so
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c8c  00297fb8  [heap]
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c90  00000000  
07-05 10:45:14.547: INFO/DEBUG(27):     44cc8c94  aa1f3c55  /system/lib/libwebcore.so
07-05 10:45:15.077: INFO/ActivityManager(70): Starting activity: Intent { dat=content://com.simpleclock.widget/appwidgets/1 cmp=hobodroid.clock.widget/.Settings (has extras) }
07-05 10:45:15.077: WARN/ActivityManager(70): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { dat=content://com.simpleclock.widget/appwidgets/1 cmp=hobodroid.clock.widget/.Settings (has extras) }
07-05 10:45:15.577: INFO/Ads(3527): To get test ads on this device, call adRequest.addTestDevice(AdRequest.TEST_EMULATOR);
07-05 10:45:15.637: INFO/Ads(3527): adRequestUrlHtml: <html><head><script src="http://www.gstatic.com/afma/sdk-core-v40.js"></script><script>AFMA_buildAdURL({"msid":"hobodroid.clock.widget","simulator":1,"hl":"en","preqs":2,"u_so":"p","slotname":"a14e0eda6eb26ea","js":"afma-sdk-a-v4.1.0","app_name":"8.android.hobodroid.clock.widget","isu":"B3EEABB8EE11C2BE770B684D95219ECB","u_audio":4,"u_w":320,"cap":"m,a","format":"320x50_mb","u_sd":1.5,"net":"ed","u_h":533});</script></head><body></body></html>
07-05 10:45:15.877: INFO/ActivityManager(70): Displayed activity hobodroid.clock.widget/.Settings: 796 ms (total 796 ms)
07-05 10:45:16.887: INFO/ActivityManager(70): Process hobodroid.clock.widget (pid 3527) has died.
07-05 10:45:16.887: WARN/ActivityManager(70): Scheduling restart of crashed service hobodroid.clock.widget/.ClockService in 5000ms
07-05 10:45:16.897: INFO/WindowManager(70): WIN DEATH: Window{43856840 hobodroid.clock.widget/hobodroid.clock.widget.Settings paused=false}
07-05 10:45:16.937: WARN/UsageStats(70): Unexpected resume of com.android.launcher while already resumed in hobodroid.clock.widget
07-05 10:45:16.987: ERROR/ActivityThread(70): Failed to find provider info for android.server.checkin
07-05 10:45:16.987: WARN/Checkin(70): Can't log event SYSTEM_SERVICE_LOOPING: java.lang.IllegalArgumentException: Unknown URL content://android.server.checkin/events
07-05 10:45:16.997: WARN/InputManagerService(70): Got RemoteException sending setActive(false) notification to pid 3527 uid 10024

解决方案

This issue is discussed here https://groups.google.com/group/google-admob-ads-sdk/browse_thread/thread/f72ed8694a28cc7d/ced66f77ddb1e3ad and here http://groups.google.com/group/google-admob-ads-sdk/browse_thread/thread/eeb307a33a69765d. The suggested workaround is to call adView.destroy() in Activity.onDestroy(). Seems to help.

@Override
protected void onDestroy() {
    super.onDestroy();

    //workaround for AdMob crash on 1.6
    AdView adView=(AdView)findViewById(R.id.adView);
    if(adView!=null)
        adView.destroy();
}

这篇关于AdMob的反复启动应用程序时崩溃模拟器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆