我开发与显示在通知区域中的定时器(进度条和文本)的进步,服务的应用程序。我已提取下面一个简单的例子同样的问题。
I am developing an application with a service which show the progress of a timer in the notification area (with a progress bar and a text). I have extracted below a simpler example with the same problem.
本服务的code:
public class TNService extends Service {
private NotificationManager nm;
private Notification notification;
private RemoteViews remoteView;
@Override
public void onCreate () {
nm = (NotificationManager) this.getSystemService(Context.NOTIFICATION_SERVICE);
notification = new Notification(android.R.drawable.stat_sys_download,
"My notification",
System.currentTimeMillis());
remoteView = new RemoteViews(this.getPackageName(),
R.layout.notification);
remoteView.setImageViewResource(R.id.icon, android.R.drawable.stat_sys_download);
remoteView.setTextViewText(R.id.text, "");
remoteView.setProgressBar(R.id.progress, 100, 0, false);
notification.flags = Notification.FLAG_NO_CLEAR;
notification.contentView = remoteView;
notification.contentIntent = PendingIntent.getActivity(this, 0, new Intent(this,
TNActivity.class), PendingIntent.FLAG_UPDATE_CURRENT);
Timer timer = new Timer ();
timer.schedule(new TNTask(this), 0, 200);
}
@Override
public IBinder onBind(Intent arg0) {
return null;
}
public void updateNotification(int progress) {
remoteView.setProgressBar(R.id.progress, 1000, progress, false);
remoteView.setTextViewText(R.id.text, "Progress: " + progress);
nm.notify(0, notification);
}
}
一个TimerTask的code:
The code of the TimerTask:
public class TNTask extends TimerTask {
private TNService service;
private int progress;
public TNTask(TNService s) {
this.service = s;
this.progress = 0;
}
@Override
public void run() {
progress = (progress + 1) % 1000;
this.service.updateNotification (progress);
}
}
现在的问题是巨大的内存使用情况。这里是logcat的输出:
The problem is the huge memory usage. Here is the logcat output:
D/dalvikvm(11985): GC_EXPLICIT freed 1258 objects / 84016 bytes in 1157ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 52216 objects / 1900968 bytes in 130ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 49465 objects / 1805248 bytes in 125ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 53106 objects / 1909992 bytes in 134ms
D/dalvikvm(12008): GC_EXPLICIT freed 1604 objects / 100944 bytes in 90ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 53011 objects / 1937160 bytes in 135ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 49806 objects / 1817992 bytes in 143ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 49016 objects / 1769536 bytes in 135ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 53509 objects / 1941064 bytes in 145ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 49895 objects / 1842312 bytes in 146ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 48728 objects / 1774496 bytes in 150ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 47557 objects / 1701976 bytes in 146ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 53540 objects / 1903808 bytes in 156ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 48997 objects / 1784048 bytes in 158ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 48326 objects / 1776864 bytes in 158ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 47566 objects / 1742488 bytes in 169ms
D/dalvikvm( 85): GC_FOR_MALLOC freed 47606 objects / 1703416 bytes in 170ms
D/dalvikvm( 162): GC_EXPLICIT freed 11238 objects / 641368 bytes in 1064ms
我觉得这是太多的内存,并经过一段时间的电话挂起,这样的输出:
I think it is too much memory and after a while the phone hangs with this output:
D/dalvikvm( 85): GC_FOR_MALLOC freed 0 objects / 0 bytes in 241ms
I/dalvikvm-heap( 85): Clamp target GC heap from 24.008MB to 24.000MB
I/dalvikvm-heap( 85): Grow heap (frag case) to 24.000MB for 52-byte allocation
I/dalvikvm-heap( 85): Clamp target GC heap from 26.008MB to 24.000MB
D/dalvikvm( 85): GC_FOR_MALLOC freed 0 objects / 0 bytes in 241ms
I/dalvikvm-heap( 85): Clamp target GC heap from 24.008MB to 24.000MB
I/dalvikvm-heap( 85): Grow heap (frag case) to 24.000MB for 24-byte allocation
I/dalvikvm-heap( 85): Clamp target GC heap from 26.008MB to 24.000MB
D/dalvikvm( 85): GC_FOR_MALLOC freed 0 objects / 0 bytes in 247ms
I/dalvikvm-heap( 85): Clamp target GC heap from 24.009MB to 24.000MB
I/dalvikvm-heap( 85): Grow heap (frag case) to 24.000MB for 28-byte allocation
I/dalvikvm-heap( 85): Clamp target GC heap from 26.009MB to 24.000MB
D/dalvikvm( 85): GC_FOR_MALLOC freed 0 objects / 0 bytes in 247ms
I/dalvikvm-heap( 85): Clamp target GC heap from 24.009MB to 24.000MB
任何人都知道我该怎么做没有使用这么多的内存?
Anyone knows how can I do it without using so many memory?
谢谢!
我偶然发现了同样的问题......这似乎是说,如果我不高速缓存在服务中远程视窗和通知,但重新打造他们从零开始,在更新例行公事这个问题就会消失。是的,我知道这是效率不高,但至少在手机没有10-15分钟后重新启动,因为它是内存不足。
I stumbled upon the same problem... It seems like that if I don't "cache" the RemoteView and Notification in the service, but re-create them from scratch in the "update" routine this problem disappears. Yes, I know it is not efficient, but at least the phone does not reboot after 10-15 minutes because it's out of memory.
上一篇:AudioRecord记录在Android的大号断续声断续、大号、AudioRecord、Android
下一篇:Android的 - 动画视图的TOPMARGIN / bottomMargin的/ etc中的LinearLayout或RelativeLayout的视图、动画、TOPMARGIN、Android