Fusion crashing several times a day on powerful mac, anyone else?

[nathankau]

I recently read a forum post where a dev said they received 3 crash logs in the past month. In the past 24hrs Fusion has crashed for me more than 3 times. I don't usually report the crashes because after several thousand crashes over the years, it doesn't seem Fusion has been getting better nor does it seem like the Fusion team has the bandwidth to make Fusion a stable program. In the beginning I would try to submit crash reports, but it just feels like a waste of time at this point. Is anyone else in the same boat? Frustrated but with no other CAD/CAM options? I fundamentally wonder if the devs know the program is so unstable.

Crashes happen for totally varied reasons for me. Recently it's been crashing when loading models with CAM, changing a CAM operation, etc. Last week it was crashing when trying to open previous versions of a file. Other times it'll crash when changing the dimension value in a sketch. None of these are consistent triggers, and the triggers are all really all over the board. I also run Fusion on a windows workstation and it doesn't seem any more stable.

Another annoying issue that has not been solved over the 6 years I've been using Fusion on Mac is that when starting Fusion, it'll randomly became the active window as it loads in UI components one by one. It's frustrating that I can't switch over to a browser for instance while I wait for Fusion to start because the half-loaded UI will take over.

Sorry this post is essentially a rant, but I seriously want to know if the devs are aware of so many fundamental issues.

[jeff_strater]

from the Fusion team's point of view, it is important that you send in those crash reports.  We do take them seriously, and we try to fix the crashes that affect the most people.  But, if you and others are not sending those in, then we have no way of knowing that a given crash is happening, or is affecting lots of people.  So, it's up to you - don't send them in if you don't want to bother, but without that information, we cannot know the crash exists, much less fix it.

[nathankau]

Thanks for the response. I assume the dev was talking about something else when referring to 3 crash reports a month? I'd assume there are tens of thousands of crashes per month? 

Are you familiar with the bug I described when opening F360? Thanks

[nathankau]

The other issue is that F360 often hangs and doesn't let the user report a crash. This just happened to me where I attempted to simulate a CAM job, it crashed and gave me the option to send a report so I did. Then I opened F360 back up, opened the same part, tried to simulate again, and it just hung forever with no option to report. I then force-quit the application.

[jeff_strater]

90% of the time, a "hang" is not really a "hang", but instead is just a very expensive operation that can take a long time to complete.  When this happens, is the geometry or the toolpath involved complex?  I'm not familiar with CAM, but we see the same things in modeling - some operations (e.g. complex sketch or feature patterns) are just very slow to compute, but will finish if given enough time.  If you want to supply an example of such a case, the CAM team would be happy to take a look at it.

Yes, we are aware of the focus-grabbing problem and are working on it.

[nathankau]

I think this time the hang was not due to a compute-heavy operation because 1) I let it sit there for about 5 mins, and 2) I had just previously tried to simulate the CAM and it crashed immediately rather than hang. Plus, it was also only simulating a few basic ops that f360 usually has no trouble with. 

I also just got another crash 311377716 that really confused me because I literally just closed a drawing. I love F360, but that makes it 3 crashes in the past 24hrs (again).