Being the slob I am, I kept no records of where I'd read that Android 2.2.x ( Froyo) had memory management issues. These issues, in turn, caused the Droid X to reboot on occasion.
Mine did that. A lot. My Droid X would reboot about every other day. Sometimes it would reboot without warning, and other times the unit would slow to a crawl before crashing.
I had hoped these alleged memory issues would disappear with Gingerbread. So far, I'm not so sure.
My phone rebooted twice today, only a day after I'd factory reset it to fix another problem. The first time it crashed under Google Maps. Apparently, it couldn't handle the traffic layer for Washington D.C. on an early Saturday morning.
The second time, it crashed when I loaded an audio file from the NPR News program into its own player.
Okay, I realize that, despite the somewhat misleading 2.x motif, this is a fairly comprehensive rebuild, and much of the code of this allegedly open software has yet to be released to developers. If it had, Quick Settings would work like it did under 2.2. So it's possible that NPR News has some work to do to bring their audio player into line with GingerB. So we'll see.
But Maps? That's Gogle, too. And it's a huge resource hog. Despite the fact Google switched to vector graphics, it now caches more of the data on the phone, so either way it's both processor and memory hungry. And I wonder if 2.3 has the same problem moving unused programs out of RAM fast enough so necessary data won't load so fast as to collide with that being evacuated. Further, I can't be sure if Maps crashed the phone due to some hinky bit of code, or because its RAM demands bumped the phone into disaster mode.
Either way, it's still wait and see. But I'm not holding my breath.
Mike
Wishing I could read code like a newspaper