The memory "leak" thing is nothing more than a cache "optimization" in place to make the device respond snappier.
Whether it succeeds or not is another story altogether...
Basically, like any cache, it stores recent calculations for faster response later. For example, if you open and close IE alot, you might notice that the first time you open it on a fresh restart takes a little bit longer than the next times- that's because the second time you start it up, parts of it are still in memory from the first time!
You might be wondering why this happens even after forcing it closed with Xbutton or the memory settings. That's because the info stored in the performance cache aren't directly related to any one program! Many apps can use the same routines and calculations, and therefore this process exists on a processor/file system layer as opposed to a software layer, and therefore also exists even when all programs are closed!
Meaning, if I have mapopolis that uses a certain routine to access my BT GPS receiver, even after I close it, some of that routine stays in memory because perhaps Google Maps will use the same routine, and therefore respond faster!
Now, ideally, this should speed up performance, and it SHOULD disappear on its own if the memory is needed and the information goes "stale" (hasn't been processed in a while = not really needed for optimized perfomance). However, one look at the way Microsoft handles "automatically closing apps" (native X button, anyone?) is enough to know that WM can't manage its own memory very well.
I can, however, vouch for the fact that the longer you leave all programs closed, the more of your memory starts to creep back into available. I've sat and watched this happen. So, it sort of works, but perhaps not well enough if people are having low memory system crash problems.
Now, before you all start blaming MS for this... Its not Microsoft's problem. They developed CE-5 (which WM6 is based on) on machines limited to 32MB to make sure the programmers didn't get lazy with OS bloat.
Its the manufacturers who add all this file system optimization and stuff to their final device. In this case, its the way HTC thinks the system should run, which is why this anomaly is NOT as apparent on, say, a WM Treo device.
The good news is that if we complain enough, HTC might realize this optimization does more bad than good, and leave it out on the next ROM update for us.
However, truth be told, I think it works. The Mogul is one of the snappiest PPC's I've used of late, although I can't say for sure if its because of the cache or not.
This is just my personal opinion, so don't flog me! I just don't look at the memory useage anymore unless I'm having a problem, which mind you, I hardly do.
My most recent observations were this:
Soft reset gives me ~21MB (got some htc plugins), and after a day of use, making sure to close everything after I'm done, I get 18-19MB. At lowest, I hit 10MB after closing alot of apps. This memory usually comes back to 18-19mb in a matter of time for me. If for some strange reason it doesn't (can't say how often this happens), I soft reset.
All in all, I'm happy with the Mogul.
|Thread Tools||Search this Thread|