Mar
30
2010
RON Exchange Rates v3.4
This version fixes a very severe bug that made the application use a lot of CPU even if the user didn't use it.
For the developers interested in how I found it:
The Battery use tool from Android 1.6 reported my application as having the CPU total around 13 minutes, which is a huge amount for an application that usually does only one update over a day, and that update is done in under one seconds.
First thing I did was to inspect the logcat. After staring at my process, for a very long while, I noticed that the GC was invoked every 4 minutes and reported collecting 13k objects. That was odd.
Next thing, I fired the DDMS tool and used the Allocation Tracker to collect data for one minute. It turned out the I had a message dispatcher that was not stopped after the activity was paused. Bam!
Thanks DDMS, you saved important battery life! :-)
For the developers interested in how I found it:
The Battery use tool from Android 1.6 reported my application as having the CPU total around 13 minutes, which is a huge amount for an application that usually does only one update over a day, and that update is done in under one seconds.
First thing I did was to inspect the logcat. After staring at my process, for a very long while, I noticed that the GC was invoked every 4 minutes and reported collecting 13k objects. That was odd.
Next thing, I fired the DDMS tool and used the Allocation Tracker to collect data for one minute. It turned out the I had a message dispatcher that was not stopped after the activity was paused. Bam!
Thanks DDMS, you saved important battery life! :-)