Verson 2.0.7438 is unusable.

[Anonymous]

I don't know what happened with this update, but fusion is unusable right now. I've had no fewer than 12 crashes in the last 2 days. It's going to be a rough week of work if this is what I have to look forward to. 

All my crashes have occurred simply when trying to change tabs to another file, and I have been submitting reports.  This morning I was switching between tabs in an electronics design and had the crash report screen come up. I restarted the software and was trying to go through and save all the recovered files and when I switched to the third and last tab (not an electronics design, just a normal fusion design) it again crashed. I've never seen the software so unstable in my many years of using it. 

I've noticed general operation is slower too. Simple sketches seem to cause temporary hangs when changing things. There is more lag all around. Again, no idea what changed, but hopefully it's something that can be fixed. 

[Phil.E]

What email address are you putting in the dialog when you submit reports? I can't find any of your reports.

[chris.eganY2EK3]

Phil, they should all be associated with this account. I thought I was signed into this one when I made the post, but it looks like I was signed in with the account associated with my hobbyist license. 

[chris.eganY2EK3]

error report CER_214102579

That's one I sent just today when again, fusion crashed switching around between tabs. I neglected to fill in any info on that particular one because I was on a conference call, sharing my screen showing fusion when it happened and I was more interested in restarting the software to get through the call. 

[Phil.E]

Hi again.

I can only find 3 crash reports from your email address, for all time. They are in the latest version. 

Two of them point to recent issues that are fixed and going thru testing right now. We will not release the fix if it does not pass tests.

One of them points to an old issue that is not yet fixed. I'll follow up with that today.

If you could please send in every crash report it would help. When a crash repeats, and people avoid sending in all the reports, it looks to me and my automated systems that you had only one crash. The more a crash repeats, the more important it is to send in the crash reports. In your case today, I don't have enough information in the form of crash reports to form any kind  of opinion or get any new information out of it. Hopefully when the next few updates happen the stability will return for you.

If you want to follow up, please send in the crash reports and mention what you were doing each time. Let me know and I'll chase down your reports again to ensure all the issues are well documented and appropriate action taken.

[chris.eganY2EK3]

I will make a point to send them all moving forward. I was getting more and more frustrated and stopped when it kept repeating on the same set of actions. 

[Phil.E]

No worries. It's those reports and actions that help me log reports that can be fixed faster. The sooner I can repeat what you are doing, the sooner a developer can see the ticket.