View Single Post
  #2 (permalink)  
Old 01-22-2008, 01:00 PM
schettj's Avatar
schettj
morsus mihi
Offline
Location: Not from around these parts
 
Join Date: Oct 2006
Posts: 3,017
Reputation: 3616
schettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIPschettj is still contributing even after becoming a VIP
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by sudermatt View Post
This is a HUGE HUGE HUGE issue!
Well, it would be a problem if it actually existed.

There are two things at work here. The NORMAL behavior of any/every operating system is that, right after bootup, the OS has yet to allocate and load up all the various buffers it uses, nor has it started every service that is needed for normal functioning.

So, you USE it a bit, the rest of the services are started up, buffers are allocated, and then you check your memory free. 16MB. That's lower then mine (ballpark of 19-20mb for me) but, assuming once it reaches that point it *says* there, then that's your normal memory free for whatever stuff you have installed on your today screen, background process, etc.

The other thing at work is a very slow memory leak. I see it in PIE, but I still think its actually in the OS or possibly in the CDMA driver, but over many DAYS of use, I will slowly lose a mb or so of the free memory after I've made sure everything has exited. This continues, dropping a meg every few days, until I notice it and reset - the lowest mine got was about 11mb free, and PIE was pretty sluggish.

Windows Mobile 5 did not really suffer from this, or the larger amount of free program memory in WM5 hid the leak better.

Anyway, its not a HUGE HUGE HUGE issue - it's running as designed (the drop to 16mb) - it's the drop from 16 down to 10-11 that will happen in 3-6 days that's a problem. Just soft reset it every night, or morning, or every now and then. Ugly but effective.

Free memory is wasted memory, so long as the machine run fast I don't need to see "30MB free" - the problem with WM is it starts to get sluggish when memory gets low. I'd rather they fix that (someday!)
Reply With Quote