I agree but a large program in one of those languages will still have more bugs than a small one, that's just the nature of things and the increase in bugs isn't linear either in my experience.
I half agree with you. It surely shows the massive complexity of large software, for sure.
On the other hand, the tool should help prevent these issues. Altium has visible exceptions and lots of memory leaks that are much easier to prevent or solve with modern development tools and languages.
Also, C aged badly, but the tools (ecosystem seems to be the hip name nowadays) for C evolved, and in a smaller scale, even the language itself has evolved. Object Pascal and Delphi doesn't seem to be catch up so well.
Modern Delphi has a simple flag that you can set that will show you a log of every memory leak in your application when you shut it down, and there are 3rd party exception handling and profilers/analyzers that can be purchased for a few hundred dollars that will take care of finding/fixing AVs/performance bottlenecks. It's actually quite easy to create solid and reliable applications using Delphi if you follow solid software development practices.
The thunar-crashing thing was introduced. A few years back it was stable, then sometime around a year or 2 ago it broke. Sad to see a good piece of software take a step back (proper testing should have prohibited that, shouldn't it ?).
I get regular crashes with a bunch of stuff (everything from Thunar (don't think that shows C has aged badly), Chrome (C++) and Intellij (Java).