Quote - DaleB - could you explain the above a bit more simply :blushing:  I usually see an error when Vue crashes to a  reference involving MS C++ runtime.

Thanks :)

 

Okaydokey! Developers tend to have a lot of stuff =not= on their systems, such as codecs, quicktime, games, etc, unless it related directly to the job they are doing. As a result, things like the system registry looks markedly different than what a general user would have. Dev machines tend to be as lean in add ons as possible, to provide the most resources for coding and debugging. If you search on the Microsoft sight, you should find links to the MS Visual C++ runtime distributable executable. This is the core dll set that Visual C++ uses in doing Windows manipulation of C++ code (there is also one for the Visual Basic runtime, but that -shouldn't- be needed). A lot of programs written in C++ on Windows makes calls that aren't included in the actual Windows program, but do exist in the runtime dll's. Without those dll's to talk with, those programs either default to things like basic Windows memory management (nuff said) and stack accessing, or simply won't initialize at all, throwing error messages if you're lucky. When you install those runtimes it changes things in the basic Windows environment; traceback functions are enabled, stack accessing gets a few more calls to use, just as an example. An error involving those runtimes could be generated by the app making a bad memory call. It could be a sign that the runtime is damaged in some way, and needs to be overwritten with a clean copy of itself, or updated to a later version. Or a lot of other reasons. If your crash mentions a specific function, write it down to add to any tech ticket you submit. That will give the developer a place to start backtracing from. Is that any clearer, or just a different color of mud....? :P