<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Frequent crashes in Fusion Design, Validate &amp; Document Forum</title>
    <link>https://forums.autodesk.com/t5/fusion-design-validate-document/frequent-crashes/m-p/5499410#M304428</link>
    <description>&lt;P&gt;It's good to know that one crash-producing bug has been fixed so quickly. &amp;nbsp;Thank you. &amp;nbsp; The latency in some of Fusion's operations (which others too have noted) is one reason why I have been able to crash the system on more than a few occasions. &amp;nbsp;Basically, after selecting a command, one would naturally expect to be able to do or see something right away. &amp;nbsp;Well, if there is a longer-than-expected lag time (&amp;gt; 5 sec) before anything ostensibly happens, one would be tempted to select some other command (thinking the previous selection somehow did not register) or perhaps proceed as if the selection is already in force but with a visual delay. &amp;nbsp;Under these circumstances, Fusion can crash, or has done so for me. &amp;nbsp;This is the kind of stuff that is hard for a QA team to simulate, let alone anticipate. &amp;nbsp;Your QA people are ironically saddled with having too much knowledge of the system, so they are less likely to do the sort of crazy things that a newbie like me is more apt to try (sometime unwittingly). &amp;nbsp;Hence the need for beta testers who, by definition, do not (yet) know Fusion well. &amp;nbsp;Anyway, just my two cents. &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 08 Feb 2015 20:35:13 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-02-08T20:35:13Z</dc:date>
  </channel>
</rss>

