Exporting GEDCOM, recognize tree collapse
I am watching RootsMagic 8 import a large descendancy from Family Tree. Where there is pedigree collapse the import process does not notice and re-imports the same subtree again. This is, ahem, rather inefficient, and the larger the tree the worse it gets. RootsMagic tech support says this is controlled by FamilySearch not them.
Perhaps FamilySearch should recognize the tree collapse and stop when it encounters an "already seen" part of the tree.