Quote Originally Posted by Eric C. View Post
1. Speaking about me, I don't ALWAYS do that. But technically it's absolutely real, and not as difficult and sophisticated as you may think. "Access denied" can be handled locally, without an exception handler for that; in addition, ever heard of such things as OS kernel, drivers, R0? If so, you must not have any questions on the further.

2. Specify the kind of resources.

OS Kernel (what is it, by the way in your analogy?) would either terminate the buggy application or do nothing. It won't help the USA.exe to start working normally.
2.
COM object A has a reference to COM object B while COM object B has a reference to COM object A. No external references remain. A COM object is released when its reference counter is zero. Since object A still has at least 1 valid reference as well as object B, their reference counters cannot be zeroed. The memory won't be released until the system restarts. That IS called a memory leak. Fairly common among inexperienced programmers. And you cannot clear that memory because OS kernel won't let you. General protection fault on early systems or access denied on newer ones is guaranteed.

Back to the first off-topic. What makes you think that the USA 'developers' had put all these exception handlers before they compiled the whole stuff? What I saw in the past several weeks was more like 'dirty hacking' than even debugging.