android – GREF在多线程服务中增加/减少(aidl) – 这是什么意思？

我有一个 Android活动和使用aidl实现的服务.像冠军一样工作,我有一个回调设置将一些线程通知传递回UI,并且看起来工作正常,除了很多

GREF已增加到101,201,301,401,501等,GREF已减少.我做了一些在线搜索,发现它必须做全球参考.

08-17 02:31:19.735: DEBUG/dalvikvm(2558): GREF has increased to 301
...
08-17 02:31:25.823: DEBUG/dalvikvm(2558): GREF has increased to 401
...
08-17 02:31:36.772: DEBUG/dalvikvm(2558): GREF has increased to 501
...
08-17 02:31:42.694: DEBUG/dalvikvm(2558): GREF has increased to 601
...
08-17 02:31:48.695: DEBUG/dalvikvm(2558): GREF has increased to 701
... 
08-17 02:31:59.883: DEBUG/dalvikvm(2558): GREF has decreased to 599
08-17 02:31:59.912: DEBUG/dalvikvm(2558): GREF has decreased to 499
08-17 02:31:59.912: DEBUG/dalvikvm(2558): GREF has decreased to 399
08-17 02:31:59.912: DEBUG/dalvikvm(2558): GREF has decreased to 299
08-17 02:31:59.912: DEBUG/dalvikvm(2558): GREF has decreased to 199

我做了一些搜索,发现大部分关于此的评论相当陈旧.我担心的是我正在正确地实现我的客户端/服务,并且想知道如何跟踪导致GREF增加的原因.欢迎任何想法/建议.谢谢！

基本程序流程

Client -> Creates CallBACk
Client -> Starts service
service -> Inits & Starts CountDownTimer
service.CountDownTimer.onFinish() -> DownloadAndParse()
DownloadAndParse() -> initialize new saxrequest(),new Handler for this request.
service.Handler->beginBroadcast()
Client.CallBACkstub -> updateUI()
Client.CallBACkstub -> service.startCountDownTimer()

希望这是有道理的.我会在这里发布代码,但是有这么多不同的文件.我想我会试着把流量放到看看是否有什么明显的……我唯一能看到的可能就是重新使用saxrequest()而不是创建一个新实例……我现在会尝试,但我真的想知道GREF和垃圾收集的影响..