I can't speak for custom roms, but I can say that there are some serious resource leaks with the stock/blur configuration. I monitored my phone closely for about a month:
http://www.droidforums.net/forum/dr...what-my-android-apps-doing-behind-scenes.html
The performance definitely and noticeably degrades, but certainly not lock up or freeze in just 2 days.
I'd love to use aLogCat to monitor what these custom roms are up to.
I'm trying to get my hands on a HTC to see if sense is any better than blur re: resource leaks too.
Sent from my DROIDX using DroidForums App
Its gotta be better.... I have a really good d2g in some aspect but theres some things that it could deffinately be better with. Normally when it freezes i can just hit lock and it will unfreeze but it takes about 30 sec to unlock on that situation. I generally just reboot it when it does that so it stops. Also, my status bar will go wierd sometimes, it acts like when you press towards the top and it starts to come down but then it just flickers like it cant decide if it wants to go back up or go down and it wont lock on this. Again, does this on all roms.
I can get you a few log files if you want me too.... have to tell me how you want them set up.
Sent from my Fissioned D2G
Do NOT send your logfiles to people you don't know. There is private/personal info in there that some apps log.
I installed aLogcat and watched the logs closely as I tried my various apps, data sync, etc.
The temporary UI freezing I experienced coincided with the times the VirtualMachine was doing memory management (GC=Garbage Collect).
This occurred after days of a notorious app leaking memory (database cursor resources).
Some other app might be using/leaking (more?) resources in your case, causing the need to GC more frequently/aggressively, and slowing down the UI.
For proper analysis, the phone has to be hooked up to a PC with SDK, and the logs have to be collected over days, and frequency of GCs over time compared. Dumping the heap periodically and inspecting it will tell where the memory is getting tied up.
Java developers who fine tune Java apps know how to use Memory Profilers, etc. to do these things. I guess that skillset must be lacking at many Android app development companies.
Sent from my DROIDX using DroidForums App