All bugs don't result in a crash. Frequently they result in the application simply hanging for very long period ( I usually try to give it 10+ minutes although workflow doesn't always permit), and just simple annoying UI hiccups. That being said I managed to make it crash again today by simply trying to edit a component in place. Prior to that, the component just couldn't be made visible - it took the crash to bring it back.
This is a decent exemplar, I think a lot of new code has gone into the edit in place functionality and it has introduced a bunch of regression bugs in the external component functionality. While edit in place is awesome, delaying a release to do more regression testing seems like it would have created a more stable release and wouldn't have dampened the enthusiasm for edit in place with the new instability in external components.
With regards to UI hiccups. Yesterday, I selected a body and couldn't let go of it (it stayed attached to my pointer). For as long as I can remember trying to reorder CAM operations fails about 50% of the time. For about 3 release when you moused over a CAM chevron it would disappear and when you clicked to expanded it would select the operation and try to drag it around rather than just opening to show details.
While this is complex software and all software will have some bugs when it ships, it feels like you are pushing beta features to production and not ever sweeping up lingering technical debt. These aren't deep hidden edge conditions, they front and center vanilla software bugs that should be caught in test - most through well written automated unit or integration test.
They last thing I will say, is that end of my workflow (and I assume many others), I post and trust your software to guide a very expensive machine. Thankfully, and to your credit, that part seems extremely stable and reliable. But instability in the rest of the software is starting to give me pause on whether I should continue to trust the CAM operations.