Do All Roms with Sense 2.5 have a memory leak?

[burtonsnow8]

Originally Posted by mjh8812

IMO a memory leak would be if you loaded like Opera for instance and u had 80 mb for example free before opening it...when running u had 75 mb free...and then when u closed it u only had 77 mb free...thats what i would consider a mem leak..ive noticed even going through the settings in Manilla or just using the windows lock skyrockets my ram usage and i never get it back...after a fresh boot im about 52% after about 4 or 5 hours use im at like 64% and thats with nothing open and even sometimes a run of a ram cleaning program. and thats on the newest energy, mighty, and mr. x roms..

that is something different called memory caching. It isn't leaking, it is just saving that information so it can pull it up at a later time much quicker. Basically if you've ever gone to the music tab after inserting your SD card you will see the phone caching all the music files. Next time you go to the music tab you will see it load up right away, because all the file locations are cached. You will also notice that Sense UI takes about 2% more RAM as well. I've done it on my phone and went from 56% to 60% once I navigated to the music tab.

Basically everything on your phone gets cached.

What the user above me mentioned is a memory leak!

*edit*
Many of the new 2.5 ROMs do not have a memory leak but they do have a higher running % and cannot handle as many apps (I can do 3 really intensive apps [opera, coreplayer, and other] before running out of RAM). Also, make sure any installed apps do not create a memory leak

[Howie411]

The problem is the TP2 seems to start bogging down when it has 45mbs of memory free or less. And this typically starts to happen after not rebooting the phone in a 24hr period, with nothing running in the task manager.

I'd consider that a memory leak or at least a very slow drip.

[burtonsnow8]

Originally Posted by Howie411

The problem is the TP2 seems to start bogging down when it has 45mbs of memory free or less. And this typically starts to happen after not rebooting the phone in a 24hr period, with nothing running in the task manager.

I'd consider that a memory leak or at least a very slow drip.

Run cleanRAM to clear up cached memory.

Just an FYI, Today i decided to use my TF3D music player and my % went from 63% before and 74% after...the only way to get it to drop was by using cleanRAM. Everything was cached and since sense UI always stays loaded, the memory the app used never closed itself, thus making my %s stay at 74% with nothing in the task manager, because all those files were cached. It is not a memory leak, it is inherently built into the system to save your files. There are some fixes that can change your cache settings, most of the time they are set to 0, meaning your RAM can infinitely cache items.

[semifast]

1. memory leak is a programming error that causes a program to use increasing amounts of memory as it runs.

2. using memory for cache improves speed in terms of reloading programs and/or data. Free memory is wasted memory. As long as the cache manager works well it shouldn't slow anything down.

3. not getting exactly the same free memory back when you quit a program isn't a memory leak, it's either part of the program is still loaded, or the cache is fragmented and so doesn't read exactly the same %.

those are my opinions.

[Recursion]

Memory leak = ?

1. When available memory is allocated for use, then when no longer needed is not properly returned to available memory for subsequent use. It's usually a programming error ... failure to pass pointers to free() or similar function.

OR

2. When available memory slowly, but surely, slips away as one drinks down a fifth of tequilla.

I think option 2 sounds more fun...

[sanvara]

Originally Posted by mjh8812

IMO a memory leak would be if you loaded like Opera for instance and u had 80 mb for example free before opening it...when running u had 75 mb free...and then when u closed it u only had 77 mb free...thats what i would consider a mem leak..

How about you see the available memory dwindle over time even when no programs are open. I start out at around 80mb and later in the day I might find I have only 35mb available even though I have closed out all programs I had opened.

[gxnext]

I Highly recommend 04/10/10 WM 6.5.X ROMS.Sense 2.5.GENERIC_V4 2355 I wish I knew what the secret was but everything runs great for me, fastest smoothest experience I'v ever had with winmo. With this rom somehow I'm able to run a bunch of apps that would normally ether slow the phone to a halt or crash. With this rom I have been able to run sense ui 2.5 WITH ANIMATIONS ON! I feel like i have a new phone!

[xSD]

Originally Posted by sanvara

How about you see the available memory dwindle over time even when no programs are open. I start out at around 80mb and later in the day I might find I have only 35mb available even though I have closed out all programs I had opened.

Just because you're "closing" a program doesn't return all allocated memory when you execute initially. You also have to take into account services being run and background processes.

There are no memory leaks. Our phones just don't have enough memory to run WinMo, Sense 2.5 and multiple applications and services.

[xSD]

Originally Posted by semifast

1. memory leak is a programming error that causes a program to use increasing amounts of memory as it runs..

Also add in not releasing temporary allocated memory in stacks

[dibbson]

Ok, to clarify a little cuz people are hitting and missing here. A memory leak is one that does not stop until you run out of RAM. If it stops at some point and does not continue then it is not a leak. Can anyone trully say that an app or process has used up 100% of their RAM (and don't say yes if you've had a hundred different programs open at once, obviously you could run out of RAM that way, and that's not the point of what I was asking)? If not, then none of you have had leaks, just bad memory management from an app or process running.