Related
I think all of you have seen this.. Free program stats from around 25 Mb and keeps on going down even if you completely kill the processes. is there a tool which actually kills the resident dlls and other crap in memory.. Please advice.. i want to get out this habbit of soft reset after couple of days just to bring my memory back up where it belongs ;-)
Cheers
Zobie
Yeah, leaking memory is also one of the very few things I hate on my Wizard
I also would like to know if there is a Memory Cleaner that works like it should and not only kills open programs.
Had problem also. But the Internet Exploder was to blame. I had the history settings to 30 days. Which is the default. Back to 0 days and everything was hunkydory again.
I had problems with memory too. I had less than 1MB of storage memory left. So I went from a custom 2.17 ROM to Mr. Clean AKU 2.3 and changed the Registry setting for IE as follows:
; IE Cache to storage card
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\\Storage Card\\Temporary Internet Files"
I've used this ROM for a week now with lots of programs. I have an average of 25 MB of storage free and the system is fast.
I have experienced no problems whatsoever.
If i don't even open the IE will it still be a memory hog?? i don't understand that.. I can understand that if i use IE all the time it will cause problems but if i don't even use it why woud my memory drop with time. Cans omeone please explain. I am not trying to offend neone here but just wante dto know. I can definitely try the reg settings. Please let me know.
Thanks
Zobie
Don't confuse ROM with RAM and storage with program mem. I think the topic starter referred to his RAM mem becoming less every day, resulting in low program mem and slow operations, needing a reset to clear the RAM and speed up the device.
The IE cache is stored in ROM and will only fill your storage but not slow down your device.
memory leaks are unfortunately a standard issue with PPC devices, I have always suffered from them on both WM 2003 SE and Wm5 devices. For me a soft reset now and then clears it up, but I find it an annoying "feature" as well.
I think like Windows its the In Memory DLLs which are the culprit. I wonder if there can be tools for detailed view of memory for Xp why not WM5.
BUMP !!!
zobie said:
I think like Windows its the In Memory DLLs which are the culprit. I wonder if there can be tools for detailed view of memory for Xp why not WM5.
Click to expand...
Click to collapse
What are the "In Memory DLL's"? Never heard of such a thing.
The memory that slows your device is the addressable application memory, which is a total of 32 MB. You cannot change that or add to it.
Think of it as the same as the Virtual Memory (VM) in Windows XP on your desktop. Every application you open reserves a bit of this virtual memory. Some apps willingly give it up when they close - some that are not as well written do not. A soft reset when you see the device slowing is about all you can do.
My only other advice is that skinned applications - particularly Today screen plugins - use up this addressable memory very quickly. This includes Wisbar Advance2, PocketBreeze and iLauncher, and any weather program. If you are running these, you will always have similar issues. Find an acceptable mix of skinned apps that you must have, and try doing without the rest just to see how it treats your device's memory.
And if you want to see what processes are running, and how much memory they are using, try MemMaid by Dinarsoft or SK-Tools. Great programs.
Amen. I wonder how much is held in reserve by the system in case you start the app again? Real Windows has been doing that for a long time, I wouldn't be surprised if micro Windows did it as well. Kind of reminds me of years ago when NT would report how it actually used memory and the end result was there was almost zero bytes "free" because all memory was always used for something, it didn't let anything sit around doing nothing. But since users didn't get it, MS wrote the taskman and so on to report something as "free memory" even though it wasn't really free. Finally, a lot of apps were designed to hide, not close, when you select the "X". If one of those task manager apps just blows the app away, does it bother cleaning up after the app which wasn't given the chance to clean up after itself by closing correctly?
markgamber said:
Amen. I wonder how much is held in reserve by the system in case you start the app again? Real Windows has been doing that for a long time, I wouldn't be surprised if micro Windows did it as well. Kind of reminds me of years ago when NT would report how it actually used memory and the end result was there was almost zero bytes "free" because all memory was always used for something, it didn't let anything sit around doing nothing. But since users didn't get it, MS wrote the taskman and so on to report something as "free memory" even though it wasn't really free.
Click to expand...
Click to collapse
Take a look here to learn about what you really see in task manager regarding memory/cpu usage.
http://tinyurl.com/l57w8
Finally, a lot of apps were designed to hide, not close, when you select the "X". If one of those task manager apps just blows the app away, does it bother cleaning up after the app which wasn't given the chance to clean up after itself by closing correctly?
Click to expand...
Click to collapse
Depends on which task mamger you are using; some use the WMClose command instead of the Kill command. Big difference!
Tools Like Memmaid SK-Tools don't allow you to identify rouge elements in memory which nolonger have a parent process running. It is those elemts which eat up the memory. I have SPB tools to actually close the application but even then the memory keeps on falling. I guess there is no tool as of today like Taskmanager or even RAM Optimizer for PPC. A Tool like RAM Optimizer would check for the elements which are residing in RAM and are no longer being used. XDA developers can surely write something using the .NE Framework.
J-Mac said:
Depends on which task mamger you are using; some use the WMClose command instead of the Kill command. Big difference!
Click to expand...
Click to collapse
Do you happen to know of a couple that use the WMClose command? I've used HandySwitcher most recently and MagicButton in the past, but have no idea which method(s) they use.
Thank you.
Geoffrey
There must 40 threads on this topics by now. I concur with J-Mac that today plugins are mostly to blame. I use Journal Bar and perform a soft reset roughly every other day. To help the situation I also use 2 programs which I find invaluable - The first is Smartskey which allows you close a program rather than minimise it (its a free download on this forum). The second is SK Tools Free up RAM application which works reasonably well but only delays the enevitable soft reset. It's effectiveness decreases the longer the device remains active.
Well, I seem to have a constant memory leaking problem. I've tried different roms over the past few years. Some of the most recent DCD 3.2.4, 3.2.6, 4.1.2, and now RM v2.2 light. They all seem to have the same problem. The memory is fine when I do a soft reset, then I start using the phone for whatever, Internet, Text Messaging, etc. The memory starts to get less and less and less over a very short period of time until I hardly have any left. So, I have to keep soft resetting the phone like every hour or more. Is there a solution to this? I have to assume it's a hardware issue since all the ROMs seem to cause the same problem. I have a friend that has the same phone and he uses his phone with MR1 and he says he has no problems at all, but he uses his phone as a basic phone and doesn't use it like a computer, like I do. He doesn't text message or use many applications at all. So, I don't know if he would have the same problem if he ran all the apps I do and text messaged, etc. Thank you for your help and time...
It's not a hardware issue. Due to the nature of our OS, there will more than likely always be a slow memory leak...but it shouldn't be bad.
Do you have a task manager like HTC Task Manager that allows you to completely close apps when you press (or hold) the X? You may have lots of apps running throughout the day that don't actually exit.
You can also try running a program like Oxios Hibernate occasionally to free up some memory.
You may also have programs such a Voice Command that run in the background and use memory; try looking and seeing what is running in the background.
Try downloading something like DotFred's Task Manager, and look at the what programs are running and how much memory they utilize shortly after a reset. Then look again a few hours later to see what changes.
Yes, I do and I'm exiting the apps. It doesn't seem to be bad with this new RS ROM. All the DCD ROMs that I used had a major problem when I used them. I was using memRelease, that seemed to be the best out of the ones I tried, but it would still not release a lot and it would slowly go down lower and lower. I've just started using Oxios Hibernate 1.40 since it came with the new ROM. I don't have voice command that I know of. I see what's running in the background, there is some utility came with the ROM, but I'm not sure what the files are that are running and if it's OK to stop them. I will have to try what you say, but I'll have to try to find that utility again, or get that one you suggested. Thanks!
btonetbone said:
It's not a hardware issue. Due to the nature of our OS, there will more than likely always be a slow memory leak...but it shouldn't be bad.
Do you have a task manager like HTC Task Manager that allows you to completely close apps when you press (or hold) the X? You may have lots of apps running throughout the day that don't actually exit.
You can also try running a program like Oxios Hibernate occasionally to free up some memory.
You may also have programs such a Voice Command that run in the background and use memory; try looking and seeing what is running in the background.
Try downloading something like DotFred's Task Manager, and look at the what programs are running and how much memory they utilize shortly after a reset. Then look again a few hours later to see what changes.
Click to expand...
Click to collapse
OK, I can't find the application I was talking about, I'm thinking it was in the Heavy version of the ROM and not the Light and that's why I can't find it now.
I did what you suggested and I installed DotFred's Task Manager. I can see the processes that are starting when I do a soft reset. Can you tell me if there is a place that lists what all the processes are and what I need and don't need? This way I can figure out what processes and don't need and stop them. Is there a way to stop some processes from starting automatically when you turn on the phone, and that will only start when I start them manually?
When I do the soft reset my free memory is about 17.76 MB but my processes are only using 15851 KB but my free memory is 18.52 MB after I use Oxios. So, that doesn't work well to free up memory. After you minus the memory the proceses are using from the total memory it should have 37.44 MB free. So, I don't know what's using up the rest of the memory.
I'm also using Kernal to use the High Memory Kernal so the camera doesn't work and it frees up alot more memory. So, if I used Low Memory Kernal my memory would really suck. So, there must be something wrong here.
Is there a way to keep ActiveSync from starting all the time? Here is the list. Thank you!
shell32.exe - 4440 kb
gwes.exe - 3350 kb
device.exe - 2677 kb
services.exe - 2383 kb
filesys.exe - 1812 kb
cprog.exe - 892 kb
connmgr.exe - 104 kb
repllog.exe - 101 kb
TaskMgr.exe - 80 kb
psShutXP.exe - 5 kb
FTouchFlo.exe - 5 kb
poutlook.exe - 1 kb
NK.exe - 1 kb
btonetbone said:
It's not a hardware issue. Due to the nature of our OS, there will more than likely always be a slow memory leak...but it shouldn't be bad.
Do you have a task manager like HTC Task Manager that allows you to completely close apps when you press (or hold) the X? You may have lots of apps running throughout the day that don't actually exit.
You can also try running a program like Oxios Hibernate occasionally to free up some memory.
You may also have programs such a Voice Command that run in the background and use memory; try looking and seeing what is running in the background.
Try downloading something like DotFred's Task Manager, and look at the what programs are running and how much memory they utilize shortly after a reset. Then look again a few hours later to see what changes.
Click to expand...
Click to collapse
It must be something you're installing because I've used most of the ROMs you mentioned along with having tons of extra stuff installed and running in the background and with heavy use the memory leaks really only became a problem after a day or two... not every hour.
Well, the RM ROMs seem to be working better then the DCD ROMs. I have to keep clearning the memory, but I don't have to keep restarting my phone like I did with the DCD ROMs. I still don't understand what's up with the memory. I had like 50% clear memory after the fresh install of the new ROM, and I checked the processes. I then restore my backup and install my software and then the memory goes down to like 30% free. I check the processes and there is no new processes. So, if there is no new processes taking up the memory then what is, and how can I find out? Yes, there must be something wrong, but I don't know how to figure out what it is. Thanks!
unL33T said:
It must be something you're installing because I've used most of the ROMs you mentioned along with having tons of extra stuff installed and running in the background and with heavy use the memory leaks really only became a problem after a day or two... not every hour.
Click to expand...
Click to collapse
Since the new official WM6.5 is using a lot of RAM, does this affect the speed of the device?
Or does it merely mean that there can't be as many apps open until it reaches critical level?
Not directly, it should not. Only if it reaches a certain level, as you said.
It's likely however that WM6.5 uses more processing power than 6.1, but I can't say for sure.
It should not affect the performance, I have been up to 80% or more and never experienced any lag issues.
Cool thanks for the replies
One of the biggest misconceptions about RAM on Windows Mobile or indeed most operating systems, is that it's a good thing to have lots of free ram available. It's not. It's a complete waste of resources. The most efficient use of RAM would be bouncing off 100% used as much as possible.
It's good to have free RAM up until you have nothing more to execute. Having more RAM ensures you never reach this limit and start swapping.
I may not use all 4GB on my PC at once, but when the next version of XXXXX game comes out, I may end up using more than I do now. The overhead ensures I don't have to go out and buy more memory to ensure reliable performance.
A little off topic, but seems like a good place to ask: Opera (using 6.1, original or TESS) often struggles rendering complex (and sometimes even simple) pages. When you scroll to a new part of the page there are delays while it redraws the new bits. When you scroll back, it has to redraw the original bits. There are annoying delays and large ugly grey areas while it does this. I often have 3-4 tabs open BTW.
The question is, can Opera be allocated more memory (since I have plenty, especially since TESS) or is it completely automatic under WM? I've poked around in the registry and there are a couple of keys for "memory allocation" and "heap allocation", or some such, under the Opera section, but they're just numbers, they don't look like Mbytes, if you see what I mean.
The slow redrawing thing feels like a memory problem, as though it's redrawing from storage cache rather than quicker RAM cache, that's why I ask.
ArtieQ said:
It should not affect the performance, I have been up to 80% or more and never experienced any lag issues.
Click to expand...
Click to collapse
I fully agree with you.
The only problem is that programs that use lots of memory will not start. In fact I can play with Xtrakt only if I disable manila, otherwise the system not have enough memory to start it.
Sorry for the bad English
im sorry but if your PC or phone whatever you like is using alot of RAM, say %90, then this is going to cause the device to slow down.
once you reach a certain limit of RAM left, it has to start using disk space as temporary RAM and as such everything becomes slower.
RAM makes it quicker ONLY when the program you want is loaded into the RAM. So in windows if you have alot of programs running in the task area, then yes these programs will run up very quickly. But try then to open up another program when your memory is briming and you will find that it will slow it up.
To have memory running at a high percentage used is bad practise. In theory its good because it means things are loaded, but its only the things that are loaded that notice the speed benifits. There needs to be a cut off point.
adamrob69 said:
im sorry but if your PC or phone whatever you like is using alot of RAM, say %90, then this is going to cause the device to slow down.
once you reach a certain limit of RAM left, it has to start using disk space as temporary RAM and as such everything becomes slower.
RAM makes it quicker ONLY when the program you want is loaded into the RAM. So in windows if you have alot of programs running in the task area, then yes these programs will run up very quickly. But try then to open up another program when your memory is briming and you will find that it will slow it up.
To have memory running at a high percentage used is bad practise. In theory its good because it means things are loaded, but its only the things that are loaded that notice the speed benifits. There needs to be a cut off point.
Click to expand...
Click to collapse
Your understanding of the OS and therefore your conclusions are wrong. Desktop Windows is a different beast to Windows Mobile. When physical RAM gets low in Windows, it swaps data out to the disk. In WM it doesn't, it asks programs to close down (then forces them if none of them do), on a least recently used basis. For this reason, in WM, you might as well have applications using free RAM since they're effectively 'cached' and ready to be called up quickly. Should you start another process that requires that RAM, then the old processes will be closed very quickly. In WM, free RAM is wasted RAM.
Hi
For this reason, in WM, you might as well have applications using free RAM since they're effectively 'cached' and ready to be called up quickly. Should you start another process that requires that RAM, then the old processes will be closed very quickly. In WM, free RAM is wasted RAM.
Click to expand...
Click to collapse
Exactly Which is why having the HTC task bar shut down applications on clicking the cross is a complete waste of time. Windows Mobile is designed to leave applications loaded even when you close them, that way they are ready immediately when you want them again. This saves times and also power.
As already stated Windows Mobile will close applications automatically if required to free up some space.
Empty RAM is a complete waste, and is an argument against increasing RAM in Windows Mobile devices to silly headline amounts as even in standby that RAM has to be kept powered even if not being used.
Regards
Phil
I have noticed behaviour pointing to a memory leak on the X10 - After turning the phone on, I get less and less free memory after running ATK - over 110 MB right after turning the phone on to ~70 MB after 24+ hours.
The phone is heavily modified/customized, so it may not be an SE sw bug (ADW, Smart Keyboard, handcent, k9, etc...)
What's the best process tool you can recommend to look into this?
Let the phone handle the memory. dont worry.
+1 on that. Android its linux based and us meant to work like that. Empty memory is wasted memory.
-------------------------------------
Sent from my X10i
Android may be Linux based, but if *after killing all idle processes* memory is systematically dwindling, that means/may mean that one or more of these processes is allocating memory which it is then NOT being released - either by the process (more probable) or the system itself (less probable).
In other words, for the same set of running processes/applications , the memory usage should *not* systematically go up over time.
Linux itself has no automatic GC. Android does (Dalvik VM), but it takes some care from developers for that to work properly - no "loose" pointers to unused but still-referenced data, etc....
acmbc said:
Android may be Linux based, but if *after killing all idle processes* memory is systematically dwindling, that means/may mean that one or more of these processes is allocating memory which it is then NOT being released - either by the process (more probable) or the system itself (less probable).
In other words, for the same set of running processes/applications , the memory usage should *not* systematically go up over time.
Click to expand...
Click to collapse
I disagree, as processes are used/exercised the kernel will allocate the memory they need, after switching on the phone the processes are idle and occupy a small amount of memory. As they are used the process size will grow in main memory as they store or cache common data used by the process. That is why applications such as facebook may be slower at start off as the data needs to be supplied, once this data is cached it will run much faster as the data is already in main memory.
Linux/Android works on the principle that it's a waste not to use as much memory as possible.
Not to get into a GC flame war here: The principle you mention is right, its just that after one KILLS these processes (facebook for example) ALL OF the memory allocated by facebook should be relinquished to the system (ergo, appear as free).
I.e. if I start up my phone, and just have processes A B and C running and have lets say 120 MB free, and after using the phone for a while kill everything and *restart* ONLY processes A B and C, then I should have 120 MB free. At least tendentially (may have a different set of resident libs at the 1st and 2nd points in time, some other minor stuff may be different, etc..). However, I find that doing this over and over results in less and less free memory being available as time passes.
I am not saying I am *right* but a good process inspection tool would help to ascertain what is going on.
acmbc said:
Not to get into a GC flame war here: The principle you mention is right, its just that after one KILLS these processes (facebook for example) ALL OF the memory allocated by facebook should be relinquished to the system (ergo, appear as free).
I.e. if I start up my phone, and just have processes A B and C running and have lets say 120 MB free, and after using the phone for a while kill everything and *restart* ONLY processes A B and C, then I should have 120 MB free. At least tendentially (may have a different set of resident libs at the 1st and 2nd points in time, some other minor stuff may be different, etc..). However, I find that doing this over and over results in less and less free memory being available as time passes.
I am not saying I am *right* but a good process inspection tool would help to ascertain what is going on.
Click to expand...
Click to collapse
Wrong.. it should NOT be returned to the system.. but it should be marked as "disposable" IF another process wants to use it. That is the way linux usually do.. That is why the "Free"-value is misleading. As the "Free"-value is not the sum of "Free" and "Cached" values. when you "unload" a lib it is not completely removed from memory, it is just marked as "cached" instead. Saving tremendous ( ) amount of battery and time when, if, the user wants to use it again before overwritten by another memory-hungry application..
Regards // OwL
does all this mean we don't really need advanced task killer?
or does the advanced task killer kill the cpu process? ( as a result longer battery life)
robbyf66 said:
does all this mean we don't really need advanced task killer?
or does the advanced task killer kill the cpu process? ( as a result longer battery life)
Click to expand...
Click to collapse
advanced task killer kills the application itself, so that nothing more is executed by that application thread(s). wether dependent libraries are kept loaded or not does not affect battery time when not used. Advanced task killer does not actually unload any libraries it only kills the process.
I personally hardly never use advanced task killer, as it is not needed as long as you make sure to run applications that does not keep the phone from going into sleepmode. Those programs are just simply bad coded.. I instead have a CPU-meter application in the task-bar and if I see that the CPU-time is extensivly used after the application has been put to background, then I might use a taskkiller to stop the bad application. But that scenario is rare... I usually get 50h+ of battery time per charge, whatever I do with it.
Regards // OwL
Hi friends,
trick for increment ram free exsist? sorry my bad english
Thanks
Get yourself a task manager and kill all unnecessary processes, but I don't really know what would you use that free RAM for
Graveir said:
Get yourself a task manager and kill all unnecessary processes, but I don't really know what would you use that free RAM for
Click to expand...
Click to collapse
ok friend,
for you the best task manager?
double thanks
Use task killer its free in the market, as for me im using System panel.
allgsmnetwork said:
ok friend,
for you the best task manager?
double thanks
Click to expand...
Click to collapse
advanced task manager is the best ,but check this article out
http://phandroid.com/2011/06/16/android-psa-stop-using-task-killer-apps-now/
Android system (2.2 and 2.3--> 2.1 is not too efficent in this) frees the memory itself, and caches things like Windows 7 (but in a far effective way). If you start a software that needs more RAM, then Android frees it for the app (or it tries to free it up: sometimes you have to run more than once a memory hog app to get it started), else it's precaches system things to fasten up the phone. So. If you have a lot of memory free, it's not always good.
Note that the problem starts if the CPU "can't rest". Then will come the less battery time, slowness, choppiness, etc. So: If there is an Application that has been loaded into memory, and runs in background and eating CPU cycles, then it's not good. In this case you have to close it manually. But not for the more RAM. You have to close it because Android itself MAYBE won't close it, because it recognizes as a running task (so it isn't an idle task) that is in use, and it keeps eating the CPU-->battery.
Hope this helps for the memory-geeks