Quote:
Originally Posted by winmobilelawyer
I know this isnt the thread to be having this conversation. But my point was that there is no leak that this is what WinMo6 was designed to do, and I believe it was designed that way because MS assumed the latest phons would be 96mb of ram or higher.
|
Oh - so you're saying that it's not a memory leak, but that it's WM6 doing the normal caching that a virtual memory OS is designed to do? Perhaps ... I really don't know.
I haven't really experimented much with it (since my Titan normally gets soft resets often for other reasons), but I tend to disagree with that for the reason that I've had "out of memory" errors from the camera app only if my Titan has been running for awhile (days). If WM6 were just doing normal caching, it would release either the least recently used or oldest cached pages immediately to the camera app. Instead, it appears to think the cached memory is still actively allocated to a running process - i.e. either a mis-behaving app or an OS memory leak. Or maybe WM6 really needs more physical memory. Again, without the proper monitoring tools, I just don't know. I certainly speculate that if it's not a leak, then the problem will be worse with WM 6.1 when EVDO-A and (a)GPS are released since it's safe to assume WM 6.1 will be at least a bit more memory-hungry.
** Any WM developers out there that have access to process/memory monitoring tools in the SDK or at MSDN?