The program version is FTM 2014 with all upgrades up to date. The Gedcom was downloaded from a Family Search tree. My point here is that the Gedcom was imported and validated by FTM. At that point, FTM should have (and does) eliminate bad records with an error report. The resulting FTM file reliably crashes every time on the same operation I described. Other Gedcom processors do not flag any other errors or character problems. There are tens of thousands of database applications that run every day without crashing. Most FTM crashes appear to be due to memory management problems or lists that are too lengthy. I can identify those since they are episodic. Usually, simply restarting the program is enough. In a few cases, the crashes seem associated with Public Member source links I imported from Ancestry.com a decade ago. In one of those cases, I identified the offending data as an out-of-place NAME record in the middle of the Public Member tree source records. I can only guess there was some offending sync procedures years ago that persists in some trees like mine. However, my database has been "exported" from the Publish/Extended Family Chart and restarted using the FTM-recommended procedure, which is supposed to cure all internal data errors. I brought this particular crash to your attention because it is one of the few times I can reliably reproduce the circumstance and outcome of the crash. However, I still can't understand how viewing a list of facts could cause a crash. My database is UTF-8 characterset so any data within a fact should be handled gracefully and any data describing the structure of a fact record should have been validated by FTM on the import operation.