Java WaitForgCTOMPLETE因原因禁用而被阻止89.851ms
我有两个版本的应用程序,一个付费版和一个免费版。两个版本共享通知服务的相同代码。一个版本正在工作,另一个版本似乎在运行代码并启动方法以显示警报,但这不会向用户显示,而是在logcat中显示:Java WaitForgCTOMPLETE因原因禁用而被阻止89.851ms,java,android,garbage-collection,android-notifications,mixpanel,Java,Android,Garbage Collection,Android Notifications,Mixpanel,我有两个版本的应用程序,一个付费版和一个免费版。两个版本共享通知服务的相同代码。一个版本正在工作,另一个版本似乎在运行代码并启动方法以显示警报,但这不会向用户显示,而是在logcat中显示: 20:23:51.926 I/art: WaitForGcToComplete blocked for 5.737ms for cause DisableMovingGc 04-20 20:23:54.531 I/art: Thread[5,tid=12452,WaitingInMainSignalCatc
20:23:51.926 I/art: WaitForGcToComplete blocked for 5.737ms for cause DisableMovingGc
04-20 20:23:54.531 I/art: Thread[5,tid=12452,WaitingInMainSignalCatcherLoop,Thread*=0xb7e9eec0,peer=0x32c0a0a0,"Signal Catcher"]: reacting to signal 3
04-20 20:23:54.755 I/art: Wrote stack traces to '/data/anr/traces.txt'
在应用程序的其他方面有很多不同之处,但最近增加的一个是mixpanel跟踪,我在过去看到它与垃圾收集问题有关。这在两个应用中都存在,但在每个应用中都有不同的跟踪
我已经查看了traces.txt文件,但老实说,它很大,我不确定我在找什么。我发现了这样的事情,但没有帮助:
"ActivityManager" prio=5 tid=16 TimedWaiting
| group="main" sCount=1 dsCount=0 obj=0x12d4c9e0 self=0xb7e73020
| sysTid=579 nice=-2 cgrp=default sched=0/0 handle=0xb7e73628
| state=S schedstat=( 0 0 0 ) utm=2110 stm=2446 core=1 HZ=100
| stack=0xa396a000-0xa396c000 stackSize=1036KB
| held mutexes=
at java.lang.Object.wait!(Native method)
- waiting on <0x1b396375> (a com.android.server.am.ActivityManagerService$5)
at java.lang.Object.wait(Object.java:422)
at com.android.server.am.ActivityManagerService.dumpStackTraces(ActivityManagerService.java:4800)
- locked <0x1b396375> (a com.android.server.am.ActivityManagerService$5)
at com.android.server.am.ActivityManagerService.dumpStackTraces(ActivityManagerService.java:4777)
at com.android.server.am.ActivityManagerService.appNotResponding(ActivityManagerService.java:5018)
at com.android.server.am.BroadcastQueue$AppNotResponding.run(BroadcastQueue.java:171)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
at com.android.server.ServiceThread.run(ServiceThread.java:46)
找到了bug。这是一个相当愚蠢的错误 事实证明,如果您的android:parentActivityName=等于活动名称(复制和粘贴输入错误),则会导致各种垃圾收集错误,除非您尝试发送通知,否则您可能不会注意到这些错误。谁知道呢
void sendNotification(String message) {
Log.e(TAG, "send notification");
/*NotificationCompat.Builder mBuilder =
(NotificationCompat.Builder) new NotificationCompat.Builder(this)
.setSmallIcon(R.drawable.ic_notification_icon)
.setContentTitle(message)
.setContentText("since you last serviced your shocks")
.setColor(0xffCDDC39)
.setAutoCancel(true);
Intent resultIntent = new Intent(this, ActivitiesActivity.class);
TaskStackBuilder stackBuilder = TaskStackBuilder.create(this);
stackBuilder.addParentStack(ActivitiesActivity.class);
stackBuilder.addNextIntent(resultIntent);
PendingIntent resultPendingIntent =
stackBuilder.getPendingIntent(
0,
PendingIntent.FLAG_UPDATE_CURRENT
);
mBuilder.setContentIntent(resultPendingIntent);
NotificationManager mNotificationManager =
(NotificationManager) getSystemService(Context.NOTIFICATION_SERVICE);
mNotificationManager.notify(mId, mBuilder.build());*/
}