This is understandable. But why not just roll back to the stable version then (r265)?
This will cause more problems than it solves, because any project saved in r266+ cannot be opened in r265. It would result in absolute chaos. If we modified r265 to try to avoid this, we would have to issue a new release, and that means we're not actually using r265 any more.
If you look at the changelogs, there have only been minor changes since r265, and mostly to the runtime. As it stands I have no idea what could have changed that would result in the kinds of stability issues people are reporting. We already made a significant upgrade to our third-party UI library in r268 as an attempt to resolve this, and as I recall the initial reports were that improved things. However there appear to still be issues being reported, although it's not particularly clear which versions are affected, because this post initially referred to r267 (prior to that change) and people aren't consistently referring to exact versions (again critical information we require in bug reports). Maybe something changed in our build system, but there has not been any intentional change there, so I don't know where to look or what to do about it - as always, being able to reliably reproduce an issue and investigate it via debugging is critical to identify what could be done about it.
Long, confusing threads like this usually actually make it harder to deal with issues. We need concise, accurate, comprehensive information to be able to investigate reports. As I mentioned it's very difficult to make sense of a thread initially relating to r267, but with new vague reports of something possibly wrong in an often unspecified version. Are lots of people still using r267 and complaining of stability issues that are already fixed? I can't tell from this. I'd strongly recommend starting a new thread that relates to issues in r269 specifically, and do everything possible to identify the systems, circumstances, configuration, version, steps to reproduce, and everything else that helps identify bug reports. I'm still perfectly willing to investigate crashes and stability issues in C2, but if there is no useful information to follow up on, there's simply nothing that can be done.