随机获得D / OpenGLRenderer:刷新缓存(模式0)的棒棒糖 [英] Randomly getting D/OpenGLRenderer﹕ Flushing caches (mode 0) in lollipop
问题描述
我面对这个问题,即我们的应用程序在结帐过程随机崩溃,只发生在棒棒糖此崩溃,它工作正常等版本。目前除了致命的信号日志猫的信息。另外这个问题不能模拟器上进行复制,它只发生在设备运行的棒棒糖。
我重构网络电话,现在我得到OpenGL渲染:刷新缓存的问题。这种情况使得一些抽射请求后。
06-22 18:48:29.876 24145-24216 / com.pangea.android.debug D / OpenGLRenderer:刷新缓存(模式0)
06-22 18:48:29.877 24145-24157 / com.pangea.android.debug A / libc中:致命的信号11(SIGSEGV),code 2,TID 24157故障地址0x12c7c000(FinalizerDaemon)
有关我使用的排球和OkHttp网络协议栈
排球请求是简单的GET请求。
是否有关于如何获取崩溃的更多信息,有什么建议?
下面是示例codeS创建连接:
保护HttpURLConnection类的createConnection(网址URL)抛出IOException
HttpURLConnection的连接=新OkUrlFactory(mClient)。开(URL);
返回连接;
} 私人HttpURLConnection类的openConnection(URL网址,请求<>要求)抛出IOException
HttpURLConnection的连接=的createConnection(URL); INT timeoutMs = request.getTimeoutMs();
connection.setConnectTimeout(timeoutMs);
connection.setReadTimeout(timeoutMs);
connection.setUseCaches(假);
connection.setDoInput(真); //使用调用者提供定制SSLSocketFactory的,如果有的话,对于HTTPS
如果(https开头.equals(url.getProtocol())及和放大器;!mSslSocketFactory = NULL){
((HttpsURLConnection的)连接).setSSLSocketFactory(mSslSocketFactory);
} 返回连接;
}
下面是logcat的:
06-18 18:08:39.427 915-915 /? D / WIFI_ICON:WifiActivity:3
06-18 18:08:39.427 915-915 /? D / StatusBar.NetworkController:dumpIcon [(消失)stat_sys_5signal_5 |空stat_sys_wifi_signal_inandout_4(消失)F]
06-18 18:08:39.627 1006年至1016年/ com.pangea.android.debug W /艺术:暂停所有线程了:33.602ms
06-18 18:08:39.657一○○六年至1021年/ com.pangea.android.debug I /艺术:背景部分并发标记扫描GC释放67796(3MB)AllocSpace对象,3(150KB)LOS对象,40%免费,12MB / 21MB,暂停5.066ms总149.122ms
06-18 18:08:39.667 1006年至1018年/ com.pangea.android.debug A / libc中:致命的信号11(SIGSEGV),code 1,在TID 1018故障地址0x656d616c(FinalizerDaemon)
06-18 18:08:39.667 1006年至1018年/ com.pangea.android.debug W / libc的:安全级别:(1),调试inforamtion由DUMPABLE标志控制。
06-18 18:08:39.667 11804-11804 /? I / DEBUG:*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** * **
06-18 18:08:39.667 11804-11804 /? I / DEBUG:建立指纹:HTC / htc_asia_tw / dlxpul:5.0.2 / LRX22G / 507296.103:用户/释放键
06-18 18:08:39.667 11804-11804 /? I / DEBUG:修订:'2'
06-18 18:08:39.667 11804-11804 /? I / DEBUG:ABI:ARM
06-18 18:08:39.667 11804-11804 /? I / DEBUG:PID:1006 TID:1018,姓名:FinalizerDaemon>>> com.pangea.android.debug<<<
06-18 18:08:39.667 11804-11804 /? I / DEBUG:11(SIGSEGV),code 1(SEGV_MAPERR),故障地址0x656d616c
06-18 18:08:39.687 11804-11804 /? I / DEBUG:R0,R1 b7982668 R2 00000000 00000000 00000000 R3
06-18 18:08:39.687 11804-11804 /? I / DEBUG:R4 b7982668 R5 656d616e R6 12c638a0 R7 FFFFFFFF
06-18 18:08:39.687 11804-11804 /? I / DEBUG:R8 70c07e38 R9 b738d940 SL 12c9a1f0 FP 12c638a0
06-18 18:08:39.687 11804-11804 /? I / DEBUG命令ip b6ea10ec SP b455aa78 LR b6bcf17f PC 656d616c CPSR 60070010
06-18 18:08:39.687 11804-11804 /? I / DEBUG:回溯:
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#00件656d616c<&不明GT;
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#01件0002017d /system/lib/libbinder.so(机器人::包裹:: freeDataNoInit()+ 22)
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#02件000201a3 /system/lib/libbinder.so(机器人::地块::〜地块()+ 4)
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#03件00080683 /system/lib/libandroid_runtime.so
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#04件000173c9 /data/dalvik-cache/arm/system@framework@boot.oat
06-18 18:08:40.158 915-915 /? I / RemoteViews:重新:com.tmobile.pr.mytmobile 1月15日
06-18 18:08:40.428 653-653 /? E / WifiTrafficPoller:TRAFFIC_STATS_POLL真正的令牌244 NUM客户13
06-18 18:08:40.428 653-653 /? E / WifiTrafficPoller:包计数的Tx = 111024 =接收151852
06-18 18:08:40.468 3087-3187 /? W / SQLiteCursor:对空关闭游标android.database.sqlite.SQLiteCursor@19398b3两次或两次以上
06-18 18:08:40.468 3087-3187 /? W / SQLiteCursor:对空关闭游标android.database.sqlite.SQLiteCursor@31d0be70两次或两次以上
06-18 18:08:40.758 271-828 /? E / QC-NETMGR-LIB:NL收到味精,recvmsg返回64
06-18 18:08:40.758 271-828 /? E / QC-NETMGR-LIB:接收到的命令:ID = NETMGR_KIF_MSG_CMD,链接= 8
06-18 18:08:40.758 271-828 /? E / QC-NETMGR-LIB:NL收到味精,recvmsg返回64
06-18 18:08:40.758 271-828 /? E / QC-NETMGR-LIB:接收到的命令:ID = NETMGR_KIF_MSG_CMD,链接= 8
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:Process命令:ID = NETMGR_KIF_MSG_CMD,链接= 8,状态= 1
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:处理RTM_NEWADDR
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:元信息:家庭= 10 prefixLen = 64 =范围指数为0x0 = 13标志=为0x0]
06-18 18:08:40.758 271-679 /? I / QC-NETMGR-LIB:属性:prefixIPv6地址[2601:0240:D100:9900:867a:88ff:fe77:631C]
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:属性:地址缓存信息 - prefered = 7200 =有效7200 cstamp = 0x3924d8 TSTAMP = 0x50cfc1
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:RCVD网络链路味精型[20]
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:无法识别的ifIndex 13
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:Process命令:ID = NETMGR_KIF_MSG_CMD,链接= 8,状态= 1
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:处理RTM_NEWADDR
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:元信息:家庭= 10 prefixLen = 64 =范围指数为0x0 = 13标志=为0x1] TEMPORARY
06-18 18:08:40.758 271-679 /? I / QC-NETMGR-LIB:属性:prefixIPv6地址[2601:0240:D100:9900:FDAD:B042:7f6c:e7cc]
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:属性:地址缓存信息 - prefered = 7200 =有效7200 cstamp = 0x3924d8 TSTAMP = 0x50cfc1
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:RCVD网络链路味精型[20]
06-18 18:08:40.758 271-679 /? E / QC-NETMGR-LIB:无法识别的ifIndex 13
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet +,HN 38(0x323630313a3234),SN(),提示(已知),家庭0,4旗
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet-,SUCCESS
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet +,HN 38(0x323630313a3234),SN(),提示(已知),家庭0,4旗
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet-,SUCCESS
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet +,HN 16(0x323030313a3535),SN(),提示(已知),家庭0,4旗
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet-,SUCCESS
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet +,HN 16(0x323030313a3535),SN(),提示(已知),家庭0,4旗
06-18 18:08:40.758 653-723 /? D / libc中:[NET] android_getaddrinfofornet-,SUCCESS
06-18 18:08:40.828 653-3231 /? E / ActivityManager:应用程序崩溃!工艺:com.pangea.android.debug
06-18 18:08:40.828 653-722 /? I / BootReceiver:复制/数据/墓碑/ tombstone_03到DropBox的(SYSTEM_TOMBSTONE)
06-18 18:08:40.828 653-2659 /? E /共享preferencesImpl:无法共享preferences创建目录文件shared_ preFS / log_files.xml
06-18 18:08:40.828 653-3231 /? W / ActivityManager:强制完成活动com.pangea.android.debug / com.pangea.android.ui.activities.MainActivity
06-18 18:08:40.878 653-3231 /? D / PMS:acquireWL(382218fc):PARTIAL_WAKE_LOCK ActivityManager推出为0x1 653 1000空
06-18 18:08:40.898 653-1400 /? I / ActivityManager:收件人1006
06-18 18:08:40.898 653-1098 /? I /的WindowState:WIN死亡:窗口{1b796396 U0 com.pangea.android.debug / com.pangea.android.ui.activities.MainActivity}
06-18 18:08:40.908 653-724 /? D / StatusBarManagerService:setSystemUiVisibility(为0x0)
看来系统发生故障实例包裹
的参考,当它在背景或在您的案件片段状态来源于/
跟踪说它失败,创造了新的实例之前释放内存。
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#00件656d616c<&不明GT;
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#01件0002017d /system/lib/libbinder.so(机器人::包裹:: freeDataNoInit()+ 22)
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#02件000201a3 /system/lib/libbinder.so(机器人::地块::〜地块()+ 4)
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#03件00080683 /system/lib/libandroid_runtime.so
06-18 18:08:39.687 11804-11804 /? I / DEBUG:#04件000173c9 /data/dalvik-cache/arm/system@framework@boot.oat
检查线路 293 及功能 freeDataNoInit()
I am facing this issue where our app crashes randomly through the checkout process, this crash occurs only on lollipop, other version it works fine. There is no information in the log cat except Fatal Signal. Also this issue cannot be reproduced on emulator, it only occurs on the device running lollipop.
I refactored the network calls and now I am getting OpenGL Renderer: Flushing caches issue. This happens after making some volley requests.
06-22 18:48:29.876 24145-24216/com.pangea.android.debug D/OpenGLRenderer﹕ Flushing caches (mode 0)
06-22 18:48:29.877 24145-24157/com.pangea.android.debug A/libc﹕ Fatal signal 11 (SIGSEGV), code 2, fault addr 0x12c7c000 in tid 24157 (FinalizerDaemon)
For network stack I am using Volley and OkHttp
Volley request is simple get request.
Are there any suggestions on how to get more information on the crash?
Here is sample codes to create connection:
protected HttpURLConnection createConnection(URL url) throws IOException {
HttpURLConnection connection = new OkUrlFactory(mClient).open(url);
return connection;
}
private HttpURLConnection openConnection(URL url, Request<?> request) throws IOException {
HttpURLConnection connection = createConnection(url);
int timeoutMs = request.getTimeoutMs();
connection.setConnectTimeout(timeoutMs);
connection.setReadTimeout(timeoutMs);
connection.setUseCaches(false);
connection.setDoInput(true);
// use caller-provided custom SslSocketFactory, if any, for HTTPS
if ("https".equals(url.getProtocol()) && mSslSocketFactory != null) {
((HttpsURLConnection) connection).setSSLSocketFactory(mSslSocketFactory);
}
return connection;
}
Here is the logcat:
06-18 18:08:39.427 915-915/? D/WIFI_ICON﹕ WifiActivity: 3
06-18 18:08:39.427 915-915/? D/StatusBar.NetworkController﹕ dumpIcon[(gone) stat_sys_5signal_5|null stat_sys_wifi_signal_inandout_4 (gone) F]
06-18 18:08:39.627 1006-1016/com.pangea.android.debug W/art﹕ Suspending all threads took: 33.602ms
06-18 18:08:39.657 1006-1021/com.pangea.android.debug I/art﹕ Background partial concurrent mark sweep GC freed 67796(3MB) AllocSpace objects, 3(150KB) LOS objects, 40% free, 12MB/21MB, paused 5.066ms total 149.122ms
06-18 18:08:39.667 1006-1018/com.pangea.android.debug A/libc﹕ Fatal signal 11 (SIGSEGV), code 1, fault addr 0x656d616c in tid 1018 (FinalizerDaemon)
06-18 18:08:39.667 1006-1018/com.pangea.android.debug W/libc﹕ Security Level: (1), Debug inforamtion is controlled by the DUMPABLE flag.
06-18 18:08:39.667 11804-11804/? I/DEBUG﹕ *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-18 18:08:39.667 11804-11804/? I/DEBUG﹕ Build fingerprint: 'htc/htc_asia_tw/dlxpul:5.0.2/LRX22G/507296.103:user/release-keys'
06-18 18:08:39.667 11804-11804/? I/DEBUG﹕ Revision: '2'
06-18 18:08:39.667 11804-11804/? I/DEBUG﹕ ABI: 'arm'
06-18 18:08:39.667 11804-11804/? I/DEBUG﹕ pid: 1006, tid: 1018, name: FinalizerDaemon >>> com.pangea.android.debug <<<
06-18 18:08:39.667 11804-11804/? I/DEBUG﹕ signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x656d616c
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ r0 b7982668 r1 00000000 r2 00000000 r3 00000000
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ r4 b7982668 r5 656d616e r6 12c638a0 r7 ffffffff
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ r8 70c07e38 r9 b738d940 sl 12c9a1f0 fp 12c638a0
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ ip b6ea10ec sp b455aa78 lr b6bcf17f pc 656d616c cpsr 60070010
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ backtrace:
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #00 pc 656d616c <unknown>
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #01 pc 0002017d /system/lib/libbinder.so (android::Parcel::freeDataNoInit()+22)
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #02 pc 000201a3 /system/lib/libbinder.so (android::Parcel::~Parcel()+4)
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #03 pc 00080683 /system/lib/libandroid_runtime.so
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #04 pc 000173c9 /data/dalvik-cache/arm/system@framework@boot.oat
06-18 18:08:40.158 915-915/? I/RemoteViews﹕ reapply : com.tmobile.pr.mytmobile 1 15
06-18 18:08:40.428 653-653/? E/WifiTrafficPoller﹕ TRAFFIC_STATS_POLL true Token 244 num clients 13
06-18 18:08:40.428 653-653/? E/WifiTrafficPoller﹕ packet count Tx=111024 Rx=151852
06-18 18:08:40.468 3087-3187/? W/SQLiteCursor﹕ Close cursor android.database.sqlite.SQLiteCursor@19398b3 on null twice or more
06-18 18:08:40.468 3087-3187/? W/SQLiteCursor﹕ Close cursor android.database.sqlite.SQLiteCursor@31d0be70 on null twice or more
06-18 18:08:40.758 271-828/? E/QC-NETMGR-LIB﹕ Received nl msg, recvmsg returned 64
06-18 18:08:40.758 271-828/? E/QC-NETMGR-LIB﹕ Received command: ID=NETMGR_KIF_MSG_CMD, link=8
06-18 18:08:40.758 271-828/? E/QC-NETMGR-LIB﹕ Received nl msg, recvmsg returned 64
06-18 18:08:40.758 271-828/? E/QC-NETMGR-LIB﹕ Received command: ID=NETMGR_KIF_MSG_CMD, link=8
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Process command: ID=NETMGR_KIF_MSG_CMD, link=8, state=1
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Processing RTM_NEWADDR
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Metainfo: Family=10 PrefixLen=64 Scope=0x0 Index=13 Flags=[0x0]
06-18 18:08:40.758 271-679/? I/QC-NETMGR-LIB﹕ Attribute: PrefixIPv6 addr [2601:0240:d100:9900:867a:88ff:fe77:631c]
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Attribute: Address Cache Info - prefered=7200 valid=7200 cstamp=0x3924d8 tstamp=0x50cfc1
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Rcvd Netlink msg type [20]
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ unrecognized ifindex 13
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Process command: ID=NETMGR_KIF_MSG_CMD, link=8, state=1
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Processing RTM_NEWADDR
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Metainfo: Family=10 PrefixLen=64 Scope=0x0 Index=13 Flags=[0x1]TEMPORARY
06-18 18:08:40.758 271-679/? I/QC-NETMGR-LIB﹕ Attribute: PrefixIPv6 addr [2601:0240:d100:9900:fdad:b042:7f6c:e7cc]
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Attribute: Address Cache Info - prefered=7200 valid=7200 cstamp=0x3924d8 tstamp=0x50cfc1
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ Rcvd Netlink msg type [20]
06-18 18:08:40.758 271-679/? E/QC-NETMGR-LIB﹕ unrecognized ifindex 13
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet+,hn 38(0x323630313a3234),sn(),hints(known),family 0,flags 4
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet-, SUCCESS
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet+,hn 38(0x323630313a3234),sn(),hints(known),family 0,flags 4
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet-, SUCCESS
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet+,hn 16(0x323030313a3535),sn(),hints(known),family 0,flags 4
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet-, SUCCESS
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet+,hn 16(0x323030313a3535),sn(),hints(known),family 0,flags 4
06-18 18:08:40.758 653-723/? D/libc﹕ [NET] android_getaddrinfofornet-, SUCCESS
06-18 18:08:40.828 653-3231/? E/ActivityManager﹕ App crashed! Process: com.pangea.android.debug
06-18 18:08:40.828 653-722/? I/BootReceiver﹕ Copying /data/tombstones/tombstone_03 to DropBox (SYSTEM_TOMBSTONE)
06-18 18:08:40.828 653-2659/? E/SharedPreferencesImpl﹕ Couldn't create directory for SharedPreferences file shared_prefs/log_files.xml
06-18 18:08:40.828 653-3231/? W/ActivityManager﹕ Force finishing activity com.pangea.android.debug/com.pangea.android.ui.activities.MainActivity
06-18 18:08:40.878 653-3231/? D/PMS﹕ acquireWL(382218fc): PARTIAL_WAKE_LOCK ActivityManager-Launch 0x1 653 1000 null
06-18 18:08:40.898 653-1400/? I/ActivityManager﹕ Recipient 1006
06-18 18:08:40.898 653-1098/? I/WindowState﹕ WIN DEATH: Window{1b796396 u0 com.pangea.android.debug/com.pangea.android.ui.activities.MainActivity}
06-18 18:08:40.908 653-724/? D/StatusBarManagerService﹕ setSystemUiVisibility(0x0)
Seems that system fails instantiate Parcel
reference when it comes from/in background or in your case Fragment states.
Trace says that it fails to release memory before it creates new instance.
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #00 pc 656d616c <unknown>
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #01 pc 0002017d /system/lib/libbinder.so (android::Parcel::freeDataNoInit()+22)
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #02 pc 000201a3 /system/lib/libbinder.so (android::Parcel::~Parcel()+4)
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #03 pc 00080683 /system/lib/libandroid_runtime.so
06-18 18:08:39.687 11804-11804/? I/DEBUG﹕ #04 pc 000173c9 /data/dalvik-cache/arm/system@framework@boot.oat
Check line 293 and function freeDataNoInit()
这篇关于随机获得D / OpenGLRenderer:刷新缓存(模式0)的棒棒糖的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!