<?xml version="1.0" encoding="UTF-8" ?>
		<rss version="2.0">
			<channel>
				<title>Case 65683: Crashes in FTM 2019</title>
				<link>https://activeprospect.fogbugz.com/default.asp?65683</link>
				<description>FogBugz RSS Feed</description>
				<language>en-us</language>
				<copyright>Copyright 2000-2019 FogBugz</copyright>
		
		<item>
			<title>Case 65683: Crashes in FTM 2019</title>
			<link>https://activeprospect.fogbugz.com/?65683</link>
			<description><![CDATA[Case posted to website<br />In FTM 2019 (Family Tree Maker 2019), many users have reported experiencing crashes, which can be incredibly frustrating when working on family history projects. These crashes can occur for a variety of reasons, including software conflicts, issues with large family tree files, or problems with syncing data across multiple devices. Sometimes, the&#160;crashes in FTM 2019&#160;are triggered when attempting to perform certain tasks, such as importing large GEDCOM files, running complex searches, or opening certain media files within the tree. It’s important to keep FTM 2019 updated to ensure that any bug fixes related to crashes are applied, as newer versions of the software often resolve stability issues. Additionally, users should consider backing up their family tree data regularly to prevent data loss in case of a crash, and they may find it helpful to run diagnostic tools or adjust system settings to minimize the likelihood of these crashes occurring. Addressing any software incompatibilities, ensuring that the computer’s operating system meets the minimum requirements for FTM 2019, and optimizing the size and complexity of the family tree file can also contribute to reducing crashes and improving the overall stability of the program.]]></description>
			<author>&quot;Alex&quot; &lt;alex@activeprospect.com&gt;</author>
			<category>FogBugzCase65683</category>
			<guid>https://activeprospect.fogbugz.com/default.asp?pg=pgEditBug&amp;command=view&amp;ixBug=65683&amp;=#461941</guid>
			<pubDate>Mon, 18 Nov 2024 19:00:35 GMT</pubDate>	
			
		</item>
	
			</channel>
		</rss>
		