Still working with Tech Support. Here's the latest:
1. They asked about it being install in my "C: drive" -- yes everything's default.
2. They had me create a "test tree" from scratch -- I got bored after a dozen or so people, but it did NOT appear to hang.
3. I had recently deleted my FTM database and re-sync to the tree on Ancestry.com -- so it's a clean download/sync.
4. They asked me to re-install Microsoft Web Enhancements (WSE). I downloaded and installed the latest 3.0. (yes, I rebooted) -- same problems. (you should try this, just in case it's the cause of your issues).
Two new observations:
ONE) Possible memory leak: I reported to them that the program starts up using about 80,000K, and doing *anything* like simply viewing individuals, the memory goes up and *never* goes down, even when closing a tree. In about 10 minutes it's already up to 345,000K -- and it's not like the performance improves during this (so it's NOT cache).
TWO) I recently started my friend's tree on-line. It has minimal work done on it (read: not much screwed up on the data, yet). Tonight, I linked it into FTM and downloaded it (with the media, etc.). It only has about 70 people in it so far -- and it was experiencing the same hangs when I did anything that actually changed data. Simply poking around and viewing various individuals does not do this, but data manipulation did (fixing place names, e.g.). So, the #2 "test tree" done above, I don't think is a comprehensive test.
So, stay hopeful me hearties! It's NOT a corrupted tree -- I'll bet dollars-to-donuts it's a memory management issue; I'll get a patch/fix out of them soon (fingers crossed)!
1. They asked about it being install in my "C: drive" -- yes everything's default.
2. They had me create a "test tree" from scratch -- I got bored after a dozen or so people, but it did NOT appear to hang.
3. I had recently deleted my FTM database and re-sync to the tree on Ancestry.com -- so it's a clean download/sync.
4. They asked me to re-install Microsoft Web Enhancements (WSE). I downloaded and installed the latest 3.0. (yes, I rebooted) -- same problems. (you should try this, just in case it's the cause of your issues).
Two new observations:
ONE) Possible memory leak: I reported to them that the program starts up using about 80,000K, and doing *anything* like simply viewing individuals, the memory goes up and *never* goes down, even when closing a tree. In about 10 minutes it's already up to 345,000K -- and it's not like the performance improves during this (so it's NOT cache).
TWO) I recently started my friend's tree on-line. It has minimal work done on it (read: not much screwed up on the data, yet). Tonight, I linked it into FTM and downloaded it (with the media, etc.). It only has about 70 people in it so far -- and it was experiencing the same hangs when I did anything that actually changed data. Simply poking around and viewing various individuals does not do this, but data manipulation did (fixing place names, e.g.). So, the #2 "test tree" done above, I don't think is a comprehensive test.
So, stay hopeful me hearties! It's NOT a corrupted tree -- I'll bet dollars-to-donuts it's a memory management issue; I'll get a patch/fix out of them soon (fingers crossed)!