search

ominfowave / open-gpstracker

Automatically exported from code.google.com/p/open-gpstracker
0 stars 0 forks source link

Wake lock not released in some cases #344

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. make the app running
2. the app process gets killed when other applications need memory ()

What is the expected output? What do you see instead?
The wakeLock acquired by GPSLoggerService should be released, and the 
GPSLoggerService should be stopped. 

I am postgraduate student. I am analyzing this great app with a research 
prototype tool. We found that it is possible that GoogleLoggerMap's onDestroy() 
handler will not be called by system if other application need memory. The 
process is killed when the GoogleLoggerMap is at onStop() handler. In this 
case, the wakeLock will not be released, and GPSLoggerService will not be 
stopped properly. This may waste energy in our view.

Thanks. Looking forward to your replies.

Original issue reported on code.google.com by yepang...@gmail.com on 31 Jul 2012 at 4:57