Ron, thanks. That is a good point about the the source images I have stored in the Legacy/pictures folder not actually being in Legacy.
I think that Legacy may read and render those images in Legacy/pictures so that it can present the small pictures in the gallery. In my case that is 13 small pictures displayed in rows of 5 each. I am guessing that Legacy may be using some temporary files on disk for working storage when resizing the images for presentation in gallery format on the screen. I think something degrades in the end-to-end image processing that causes the gallery feature of Legacy to eventually get stuck consuming high amounts of CPU indefinitely after some threshold of picture count is reached in the picture gallery. Then after deleting that threshold picture from the gallery the CPU usage returns to 0%. There is always the chance that something is broken in only my computer. That is especially true if no one else has this problem. But I have not other symptoms of trouble on my machine. Since I am relatively new to Legacy, I may have done something that "broke" Legacy. But I don't know what that could be. This is very puzzling. Bill Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

