V2.0.1288 Crashes

[Doubletop_]

I was upgraded to version 2.0.12888 today and now I'm having persistant crashes. I'll admit my model isn't the tidiest but F360 wasn't crashing prior to today. It would be helpful if there were some clues as to how to resolve. Without them I don't know if my attempts to resolve are acheiving anything.

This is just a heads up, I'm not expecting any offers to fix my model thanks so I'm not going to post it.

Error log and version details in screen shots below.  Have sent the details to support as the app requests.

Pete

[Phil.E]

Thanks for sending the crash reports. This is already reported, it started a year ago, and gets about 2 crashes a day. 

[Doubletop_]

Thanks Phil

If it has been going on for over a year does that mean you are doing something about it or you are just logging the crashes? What changed a year ago to be a possible cause problem.

Even graceful degradation  would be an improvement over a message and then just shuting down.

[Doubletop_]

A bit more on what is happening in my case. Have a five subassemblies in seperate designs and I am bringing each of these into a master assembly. The sub assemblies have errors, but these have all been resolved or supressed. So no errors going into the master assembly

I have made changes in two of the subassemblies and the master assembly is reporting updates are required. The master assembly crashes when the update is attempted. I have moved the timeline marker to the very start of the timeline and selected "update external references" and Fusion 360 reports

Warning: This design contains Removed components which did not update. To complete the update, roll the history marker to before the earliest Remove feature and click the Get All Latest button.

2 Components are still out of date.
Please run the Get All Latest command again.

(??? What does "Remove feature " mean?)

Creating a new master assembly and bringing in one of the sub assemblies, that failed in the prevous master, works so does making a change in the sub assembly and updating the new master.

[Phil.E]

Remove is a command:

It shows up in the timeline, which is what was referred in the message.

To answer your previous question about crashes: You may not realize it, but we cannot fix every issue reported in the software. If a crash gets 2 customers a month, it will get less attention than a crash that gets 2 customers a day. If we work on a crash that gets 2 customers a month, it means we can't work on a crash that gets 2 customers a day. I'm sorry this is the case, I'd love to fix every bug and crash, but there are limits to how many developers are working on defects and how much time there is in a typical work day. Thanks for your patience. 

Without your model, there is little I can add to the bug reports for these crashes to help get them sorted out sooner. Glad you found a workaround.